Vulmon
| Product | Vulmon Search |
| Records still shown as active | 20 of 26 (checked 2026-10-30); 6 marked rejected |
| First contacted | 2026-07-23 |
| Channels tried | info@ |
| Status | No response |
Records
We checked all 26 identifiers rejected against Open WebUI on 2026-10-30. 20 Vulmon pages still present the record as a vulnerability, with a title and summary describing the defect and no rejection marker. Five of those still show a CVSS v3 score. The other 15 show no CVSS score and no VMScore, but keep the vulnerability title, the summary and an EPSS value. Six pages show the rejection reason as their summary. Each identifier below is in the REJECTED state at cve.org and at NVD:
| Identifier | Withdrawn by | Rejected since | Vulmon page | What the page shows | Our assessment |
|---|---|---|---|---|---|
| CVE-2024-7033 | huntr / Protect AI | 2026-07-16 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7034 | huntr / Protect AI | 2026-07-16 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2024-7036 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7037 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7038 | huntr / Protect AI | 2026-07-16 | vulmon.com | Active, CVSS v3 2.7 | Disposition |
| CVE-2024-7039 | huntr / Protect AI | 2026-07-16 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7040 | huntr / Protect AI | 2026-07-16 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7045 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7046 | huntr / Protect AI | 2026-08-13 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2024-7049 | huntr / Protect AI | 2026-09-11 | vulmon.com | Active, CVSS v3 5.4 | Disposition |
| CVE-2024-7053 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7806 | huntr / Protect AI | 2026-08-31 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7959 | huntr / Protect AI | 2026-07-16 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-7990 | huntr / Protect AI | 2026-08-13 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2024-7999 | huntr / Protect AI, as a duplicate of CVE-2024-53981 | 2025-04-15 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-8060 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-9840 | huntr / Protect AI, as a duplicate of CVE-2024-53981 | 2025-04-15 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2024-12534 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-12537 | huntr / Protect AI | 2026-08-13 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2024-12868 | huntr / Protect AI, as a duplicate of CVE-2024-47874 | 2025-04-15 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2025-15603 | VulDB | 2026-06-18 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2025-29446 | MITRE | 2026-06-29 | vulmon.com | Marked rejected, CVSS NA | Disposition |
| CVE-2025-63391 | MITRE | 2026-06-29 | vulmon.com | Active, no CVSS score, EPSS still shown | Disposition |
| CVE-2026-0765 | Zero Day Initiative | 2026-09-02 | vulmon.com | Active, CVSS v3 8.8 | Disposition |
| CVE-2026-0766 | Zero Day Initiative | 2026-09-02 | vulmon.com | Active, CVSS v3 8.8 | Disposition |
| CVE-2026-0767 | Zero Day Initiative | 2026-09-02 | vulmon.com | Active, CVSS v3 5.3 | Disposition |
CVE-2024-7999, CVE-2024-9840 and CVE-2024-12868 were rejected as duplicates of CVEs filed against third-party libraries.
Derived scores on withdrawn records
Vulmon computes its own figures from the record it mirrors. On 2026-08-08 each of the nine pages we then tracked carried a VMScore and an EPSS value alongside the CVSS, presented as current risk data.
CVE-2025-63391 showed CVSS 7.5 and a VMScore of 850, with a summary stating that unauthenticated remote attackers can retrieve critical configuration data without valid credentials. That claim is wrong on the code, and the identifier making it was withdrawn on 2026-06-29. The page was last updated on 2025-12-19, six months before the withdrawal.
CVE-2025-29446 showed CVSS 3.3 and a VMScore of 430. It was last updated on 2025-05-28, more than a year before the withdrawal.
A score computed from a withdrawn record is a number with nothing behind it. It is still presented in the same place, in the same format, as a score for a live finding.
Re-checked on 2026-10-30: VMScore reads NA on all 26 pages. CVE-2025-29446 now shows the rejection and no score. CVE-2025-63391 now shows no CVSS score and was last updated on 2026-10-15, but still carries the authentication-bypass title and summary with no rejection marker. EPSS is still shown on every page, including 0.24461 for CVE-2024-7959, whose page shows no rejection.
Contact log
| Date | Channel | Outcome |
|---|---|---|
| 2026-07-23 | info@ | No response |
| 2026-08-03 | info@ | No response |
| 2026-08-08 | info@ | No response |
As of 2026-08-08 every entry is unchanged.
Re-checked on 2026-10-30: three of the nine entries we tracked now show the rejection (CVE-2024-7034, CVE-2025-15603 and CVE-2025-29446). The other six still present the record as a vulnerability.
See also
- Rejected CVEs in Vulnerability Databases, the overview and how to verify any record yourself.
- Vendor Dispositions, our assessment of each identifier listed above.