Rapid7
| Product | Rapid7 Vulnerability & Exploit Database |
| Problem | The withdrawal is shown on every entry. One keeps its severity and CVSS score, and all keep their EPSS score |
| Records still shown as active | 0 of 26 (checked 2026-10-30). All 26 are marked rejected. |
| First contacted | 2026-07-23 |
| Channels tried | [email protected] |
| Status | No response, but the entry has since been corrected in part |
When we wrote on 2026-07-23 the CVE-2025-15603 entry carried the original claim with no rejection marker. As of 2026-08-08 it carries the CNA's withdrawal notice in full. We received no reply, so we cannot say whether our mail prompted the change.
Records
Re-checked on 2026-10-30: every one of the 26 identifiers rejected against Open WebUI has a Rapid7 entry. Each is titled "Undefined Security Weakness" and carries the CNA's rejection reason. CVSS v4 and v3 read N/A on 25 of them. CVE-2025-15603 still shows its CVSS v4 score, and all 26 still show an EPSS score. Each identifier below is in the REJECTED state at cve.org and at NVD:
| Identifier | Withdrawn by | Rejected since | Rapid7 page | What the page shows | Our assessment |
|---|---|---|---|---|---|
| CVE-2024-7033 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (63rd percentile) | Disposition |
| CVE-2024-7034 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 2% (83rd percentile) | Disposition |
| CVE-2024-7036 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (53rd percentile) | Disposition |
| CVE-2024-7037 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (62nd percentile) | Disposition |
| CVE-2024-7038 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (27th percentile) | Disposition |
| CVE-2024-7039 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (47th percentile) | Disposition |
| CVE-2024-7040 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (43rd percentile) | Disposition |
| CVE-2024-7045 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (33rd percentile) | Disposition |
| CVE-2024-7046 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (33rd percentile) | Disposition |
| CVE-2024-7049 | huntr / Protect AI | 2026-09-11 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (28th percentile) | Disposition |
| CVE-2024-7053 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (49th percentile) | Disposition |
| CVE-2024-7806 | huntr / Protect AI | 2026-08-31 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (39th percentile) | Disposition |
| CVE-2024-7959 | huntr / Protect AI | 2026-07-16 | rapid7.com | Marked rejected, CVSS N/A, EPSS 24% (98th percentile) | Disposition |
| CVE-2024-7990 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (56th percentile) | Disposition |
| CVE-2024-7999 | huntr / Protect AI, as a duplicate of CVE-2024-53981 | 2025-04-15 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (16th percentile) | Disposition |
| CVE-2024-8060 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (57th percentile) | Disposition |
| CVE-2024-9840 | huntr / Protect AI, as a duplicate of CVE-2024-53981 | 2025-04-15 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (27th percentile) | Disposition |
| CVE-2024-12534 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (54th percentile) | Disposition |
| CVE-2024-12537 | huntr / Protect AI | 2026-08-13 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (56th percentile) | Disposition |
| CVE-2024-12868 | huntr / Protect AI, as a duplicate of CVE-2024-47874 | 2025-04-15 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (16th percentile) | Disposition |
| CVE-2025-15603 | VulDB | 2026-06-18 | rapid7.com | Marked rejected, CVSS v4 2.9 Low still shown, EPSS 0% (20th percentile) | Disposition |
| CVE-2025-29446 | MITRE | 2026-06-29 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (8th percentile) | Disposition |
| CVE-2025-63391 | MITRE | 2026-06-29 | rapid7.com | Marked rejected, CVSS N/A, EPSS 1% (42nd percentile) | Disposition |
| CVE-2026-0765 | Zero Day Initiative | 2026-09-02 | rapid7.com | Marked rejected, CVSS N/A, EPSS 2% (74th percentile) | Disposition |
| CVE-2026-0766 | Zero Day Initiative | 2026-09-02 | rapid7.com | Marked rejected, CVSS N/A, EPSS 26% (98th percentile) | Disposition |
| CVE-2026-0767 | Zero Day Initiative | 2026-09-02 | rapid7.com | Marked rejected, CVSS N/A, EPSS 0% (17th percentile) | Disposition |
CVE-2024-7999, CVE-2024-9840 and CVE-2024-12868 were rejected as duplicates of CVEs filed against third-party libraries.
EPSS estimates the probability of exploitation activity in the next thirty days, and vulnerability-management tooling reads it to decide what to patch first. Rapid7 still shows 26% for CVE-2026-0766 and 24% for CVE-2024-7959, both in the 98th percentile, for identifiers their CNAs have withdrawn.
The withdrawal is on the page
The CVE-2025-15603 entry reproduces the rejection, including the vendor explanation the CNA recorded alongside it: that the default value concerned was unreachable on every supported deployment path, and could only be reached by invoking uvicorn directly, which is unsupported.
The severity did not follow
| Field | Value shown |
|---|---|
| Title | "Undefined Security Weakness" |
| Severity | LOW |
| CVSS v4 base score | 2.9 |
| CVSS v4 vector, as published | AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P |
A withdrawn identifier has no severity, because there is no finding left to rate. This one is rated Low, with a full vector, on a record whose own description states that it was withdrawn as not a security issue. The vector carries an Exploit Maturity value of E:P, a Threat metric describing the maturity of exploit code, published against an identifier for which the CVE Program recognises no vulnerability.
Re-checked on 2026-10-30, all four values are still shown. The score matches what the CNA assigned before withdrawing. The rejection is carried as prose, and every structured field beside it still describes a finding.
The title compounds it slightly. "Undefined Security Weakness" names no weakness class, so a withdrawn record is headed by a label asserting that a weakness exists while declining to say which.
Contact log
| Date | Channel | Outcome |
|---|---|---|
| 2026-07-23 | [email protected] | No response |
| 2026-08-03 | [email protected] | No response |
| 2026-08-08 | [email protected] | No response. The entry now carries the withdrawal notice, with the severity and score unchanged. |
See also
- Rejected CVEs in Vulnerability Databases, the overview and how to verify any record yourself.
- CVE-2025-15603 vendor disposition
- Vendor Dispositions, our assessment of each identifier listed above.