Skip to main content

INCIBE-CERT

ProductINCIBE-CERT early-warning vulnerability listing (Spain's national CERT)
ProblemWithdrawn records keep their CVSS scores and severity ratings, one is presented at 9.00 CRITICAL, and one carries no rejection notice at all
Records still shown as active1 of 26 (checked 2026-10-30). The other 25 are marked rejected and still show a CVSS 3.x score.
First contacted2026-08-08
Channels triedempresas@
StatusAwaiting response
note

This page is not a general complaint about INCIBE-CERT's data quality. It concerns one specific and consequential gap.


A withdrawn record, presented as CRITICAL by a national CERT​

Start with the single entry that shows what the gap costs. Four parties have assessed CVE-2024-7053, and this is where each of them landed:

SourceAssessment
The CVE record on cve.orgREJECTED since 2026-08-13
The issuing CNA, at assignment7.6 High
Open WebUIThe described chain cannot occur, for four independent reasons
INCIBE-CERT, today9.00 CRITICAL

The highest score of the four is the one published by the national CERT. It exceeds what the issuing CNA itself claimed, on an identifier that same CNA has since withdrawn, describing an attack chain that could never have run.

The order matters. The CNA assigned it at 7.6. NVD scored it 9.0 on 2025-04-01, and INCIBE-CERT displays that score. The CNA then withdrew the record entirely, and the NVD score was removed with it. The rating that survives on the early-warning listing is one nobody stands behind any longer: the CNA retracted the record, NVD dropped its score and we never agreed with either.

A 9.00 CRITICAL is not a filing detail. It is the number that decides whether a security team drops what it is doing, whether a procurement review blocks, and whether a scanner escalates a build. Organisations read a national CERT's early-warning listing as guidance on what to act on, which is precisely the weight this entry carries and precisely what makes it costly. Our full assessment is on the disposition page.


The rejection reaches the description and stops there​

INCIBE-CERT does ingest reject transitions into the description field. On a withdrawn record the description is replaced with the CNA's notice, and nothing else on the page changes. We checked all 26 identifiers rejected against Open WebUI on 2026-10-30. Every entry still displays a CVSS 3.x vector, a base score and a severity label, and one still carries its original description. Each identifier below is in the REJECTED state at cve.org and at NVD:

IdentifierWithdrawn byRejected sinceDescription fieldSeverity still shownOur assessment
CVE-2024-7033huntr / Protect AI2026-07-16Rejection notice7.20 HIGHDisposition
CVE-2024-7034huntr / Protect AI2026-07-16Rejection notice7.20 HIGHDisposition
CVE-2024-7036huntr / Protect AI2026-08-13Rejection notice7.50 HIGHDisposition
CVE-2024-7037huntr / Protect AI2026-08-13Rejection notice7.20 HIGHDisposition
CVE-2024-7038huntr / Protect AI2026-07-16Rejection notice2.70 LOWDisposition
CVE-2024-7039huntr / Protect AI2026-07-16Rejection notice6.70 MEDIUMDisposition
CVE-2024-7040huntr / Protect AI2026-07-16Rejection notice4.90 MEDIUMDisposition
CVE-2024-7045huntr / Protect AI2026-08-13Rejection notice4.30 MEDIUMDisposition
CVE-2024-7046huntr / Protect AI2026-08-13Rejection notice4.30 MEDIUMDisposition
CVE-2024-7049huntr / Protect AI2026-09-11Rejection notice5.40 MEDIUMDisposition
CVE-2024-7053huntr / Protect AI2026-08-13Rejection notice9.00 CRITICALDisposition
CVE-2024-7806huntr / Protect AI2026-08-31Rejection notice8.80 HIGHDisposition
CVE-2024-7959huntr / Protect AI2026-07-16Rejection notice7.70 HIGHDisposition
CVE-2024-7990huntr / Protect AI2026-08-13Rejection notice8.40 HIGHDisposition
CVE-2024-7999huntr / Protect AI, as a duplicate of CVE-2024-539812025-04-15Rejection notice7.50 HIGHDisposition
CVE-2024-8060huntr / Protect AI2026-08-13Rejection notice8.10 HIGHDisposition
CVE-2024-9840huntr / Protect AI, as a duplicate of CVE-2024-539812025-04-15Rejection notice7.50 HIGHDisposition
CVE-2024-12534huntr / Protect AI2026-08-13Rejection notice7.50 HIGHDisposition
CVE-2024-12537huntr / Protect AI2026-08-13Rejection notice7.50 HIGHDisposition
CVE-2024-12868huntr / Protect AI, as a duplicate of CVE-2024-478742025-04-15Rejection notice7.50 HIGHDisposition
CVE-2025-15603VulDB2026-06-18Original description, no rejection3.70 LOW, plus 2.90 LOW (CVSS 4.0) and 2.60 LOW (CVSS 2.0)Disposition
CVE-2025-29446MITRE2026-06-29Rejection notice3.30 LOWDisposition
CVE-2025-63391MITRE2026-06-29Rejection notice7.50 HIGHDisposition
CVE-2026-0765Zero Day Initiative2026-09-02Rejection notice8.80 HIGHDisposition
CVE-2026-0766Zero Day Initiative2026-09-02Rejection notice8.80 HIGHDisposition
CVE-2026-0767Zero Day Initiative2026-09-02Rejection notice6.50 MEDIUMDisposition

CVE-2024-7999, CVE-2024-9840 and CVE-2024-12868 were rejected as duplicates of CVEs filed against third-party libraries.

A rejected record cannot have a severity​

A CVSS score is a statement that a vulnerability exists and that this is how bad it is. When the issuing CNA withdraws an identifier it is stating that there is no vulnerability. A page that carries both is asserting two contradictory things, and it resolves the contradiction differently depending on who is reading:

  • A person who opens the page and reads the description learns the record is dead.
  • Anything consuming the data programmatically may take the severity and the vector and never see the description at all. Scores are the fields built for machines: they are structured, comparable and sortable, which is exactly why tooling reads them and prose summaries get skipped.

There is also no uniform, machine-readable rejected state anywhere on the entry. The withdrawal exists only as English text inside a free-form description field, and the surrounding fields still describe a live finding. A consumer that wants to filter withdrawn records out has nothing dependable to filter on.

Of the 25 entries that carry the rejection notice, 16 are still labelled HIGH, the highest at 8.80, and CVE-2024-7053 is labelled CRITICAL at 9.00.

Some of those figures differ from what the issuing CNA assigned, in both directions. CVE-2024-7033 and CVE-2024-7034 are shown at 7.20 High against a CNA score of 6.5 Medium, and CVE-2024-7039 is shown at 6.70 Medium against a CNA score of 8.3 High. These are NVD's assessments rather than INCIBE-CERT's own, and NVD publishes them alongside the CNA's rather than in place of it. The direction of any individual figure matters less than the fact underneath all of them: a withdrawn identifier is still being presented with a severity at all.


One record carries no rejection at all​

CVE-2025-15603 was withdrawn by VulDB on 2026-06-18. The INCIBE-CERT entry was last modified on 2026-04-29 and has not been touched since, so it still carries the original text in full:

A security vulnerability has been detected in open-webui up to 0.6.16. [...] It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used.

Three CVSS scores accompany it, across versions 2.0, 3.1 and 4.0. There is no indication anywhere on the page that the identifier no longer exists.

Re-checked on 2026-10-30, the entry is unchanged: still last modified on 2026-04-29, with the original text and all three scores. The 25 other entries all carry the rejection notice, with Last modified dates as late as 2026-10-16. Whatever updated them did not reach this one, and nothing has flagged the omission in the more than four months since the withdrawal.


Contact log​

DateChannelOutcome
2026-08-08empresas@Awaiting response

What would fix this​

Removing the fields a withdrawn record cannot have. A rejected identifier has no severity, no base score and no vector, because there is no finding left to rate. Those fields should come off the entry when the withdrawal is ingested, rather than being left standing beside it. Exposing the rejected state as a structured field, instead of only as English inside a description, would then let anything reading the data act on it.

The transition is already ingested. What remains is deleting what it invalidates.


See also​

This content is for informational purposes only and does not constitute a warranty, guarantee, or contractual commitment. Open WebUI is provided "as is." See your license for applicable terms.