BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-6790High confidence

Eclipse Foundation Eclipse Jetty — Improper Input Validation

Eclipse Foundation · Eclipse Jetty

5.3MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.31% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Eclipse Foundation Eclipse Jetty and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcejetty12Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian trixietrixie · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcejetty12Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcejetty12Vendor fix publishedDebian records a fixed source-package version for this release.12.0.39-1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcejetty9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejetty9Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 7 Oct 2026
Open-source package ranges10 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.eclipse.jetty:jetty-serverECOSYSTEM: introduced 9.4.0.v20161208; last affected 9.4.58.v20250814Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-serverECOSYSTEM: introduced 10.0.0; last affected 10.0.26Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-serverECOSYSTEM: introduced 11.0.0; last affected 11.0.26Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-serverECOSYSTEM: introduced 12.0.0; fixed 12.0.3512.0.35OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.eclipse.jetty:jetty-serverECOSYSTEM: introduced 12.1.0; fixed 12.1.912.1.9OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.eclipse.jetty:jetty-server>= 9.4.0.v20161208, <= 9.4.58.v20250814Not statedGitHub advisory ↗upstream repository advisory · 22 Jul 2026
mavenorg.eclipse.jetty:jetty-server>= 10.0.0, <= 10.0.26Not statedGitHub advisory ↗upstream repository advisory · 22 Jul 2026
mavenorg.eclipse.jetty:jetty-server>= 11.0.0, <= 11.0.26Not statedGitHub advisory ↗upstream repository advisory · 22 Jul 2026
mavenorg.eclipse.jetty:jetty-server>= 12.0.0, <= 12.0.3412.0.35GitHub advisory ↗upstream repository advisory · 22 Jul 2026
mavenorg.eclipse.jetty:jetty-server>= 12.1.0, <= 12.1.812.1.9GitHub advisory ↗upstream repository advisory · 22 Jul 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-6790 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjetty: Jetty: Improper Host header validation can lead to request routing issues
42 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • jenkins.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services
  • jetty-server as a component of Red Hat AMQ Broker 7
  • jetty-server as a component of Red Hat build of Apache Camel - HawtIO 4
  • jetty-server as a component of Red Hat build of Apache Camel for Spring Boot 4
  • jetty-server as a component of Red Hat build of Apicurio Registry 3
  • jetty-server as a component of Red Hat build of Debezium 3
  • jetty-server as a component of Red Hat Data Grid 8
  • maven-site-plugin-javadoc as a component of Red Hat Enterprise Linux 7
  • maven-site-plugin.src as a component of Red Hat Enterprise Linux 7
  • resteasy-javadoc (pki-core:10.6) as a component of Red Hat Enterprise Linux 8
Summary
A flaw was found in Eclipse Jetty. The server does not strictly validate that the request authority (host and port) matches the Host header provided in HTTP/1, HTTP/2, and HTTP/3 requests. This improper validation can lead to various issues, including incorrect handling of URI constructions for redirects, flawed virtual host selection, and problems with reverse proxying. Such discrepancies could potentially be exploited to bypass security mechanisms or misroute network traffic.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-43646

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Fix not verified
01

What, why and how

In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.

What

In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2867RealObjects PDFreactor: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in RealObjects PDFreactor ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2314Eclipse Jetty: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Eclipse Jetty ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen und vertrauliche Informationen offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-59938 Référence CVE CVE-2026-60147 https://www.cve.org/CVERecord?id=CVE-2026-60147 Référence CVE CVE-2026-64958 https://www.cve.org/CVERecord?id=CVE-2026-64958 Référence CVE CVE-2026-65432 https://www.cve.org/CVERecord?id=CVE-2026-65432 Référence CVE CVE-2026-66053 https://www.cve.org/CVERecord?id=CVE-2026-66053 Référence CVE CVE-2026-66142 https://www.cve.org/CVERecord?id=CVE-2026-66142 Référence CVE CVE-2026-66143 https://www.cve.org/CVERecord?id=CVE-2026-66143 Référence CVE CVE-2026-66144 https://www.cve.org/CVERecord?id=CVE-2026-66144 Référence CVE CVE-2026-66713 https://www.cve.org/CVERecord?id=CVE-2026-66713 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-73088 https://www.cve.org/CVERecord?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-75878 https://www.cve.org/CVERecord?id=CVE-2026-75878 Référence CVE CVE-2026-7884 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-67213 Référence CVE CVE-2026-67214 https://www.cve.org/CVERecord?id=CVE-2026-67214 Référence CVE CVE-2026-67312 https://www.cve.org/CVERecord?id=CVE-2026-67312 Référence CVE CVE-2026-67313 https://www.cve.org/CVERecord?id=CVE-2026-67313 Référence CVE CVE-2026-67315 https://www.cve.org/CVERecord?id=CVE-2026-67315 Référence CVE CVE-2026-67316 https://www.cve.org/CVERecord?id=CVE-2026-67316 Référence CVE CVE-2026-67317 https://www.cve.org/CVERecord?id=CVE-2026-67317 Référence CVE CVE-2026-67318 https://www.cve.org/CVERecord?id=CVE-2026-67318 Référence CVE CVE-2026-67319 https://www.cve.org/CVERecord?id=CVE-2026-67319 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-68494 https://www.cve.org/CVERecord?id=CVE-2026-68494 Référence CVE CVE-2026-68525 https://www.cve.org/CVERecord?id=CVE-2026-68525 Référence CVE CVE-2026-68569 https://www.cve.org/CVERecord?id=CVE-2026-68569 Référence CVE CVE-2026-68763 https://www.cve.org/CVERecord?id=CVE-2026-68763 Référence CVE CVE-2026-68945 https://www.cve.org/CVERecord?id=CVE-2026-68945 Référence CVE CVE-2026-69151 https://www.cve.org/CVERecord?id=CVE-2026-69151 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-65899 Référence CVE CVE-2026-65900 https://www.cve.org/CVERecord?id=CVE-2026-65900 Référence CVE CVE-2026-66053 https://www.cve.org/CVERecord?id=CVE-2026-66053 Référence CVE CVE-2026-66142 https://www.cve.org/CVERecord?id=CVE-2026-66142 Référence CVE CVE-2026-66143 https://www.cve.org/CVERecord?id=CVE-2026-66143 Référence CVE CVE-2026-66144 https://www.cve.org/CVERecord?id=CVE-2026-66144 Référence CVE CVE-2026-66373 https://www.cve.org/CVERecord?id=CVE-2026-66373 Référence CVE CVE-2026-6733 https://www.cve.org/CVERecord?id=CVE-2026-6733 Référence CVE CVE-2026-6734 https://www.cve.org/CVERecord?id=CVE-2026-6734 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-7246 https://www.cve.org/CVERecord?id=CVE-2026-7246 Référence CVE CVE-2026-75838 https://www.cve.org/CVERecord?id=CVE-2026-75838 Référence CVE CVE-2026-8177 https://www.cve.org/CVERecord?id=CVE-2026-8177 Référence CVE CVE-2026-8400 https://www.cve.org/CVERecord?id=CVE-2026

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023680Eclipse FoundationのJettyにおける入力確認に関する脆弱性

Eclipse Jettyにおいて、HTTP/1、HTTP/2、およびHTTP/3のリクエストに対して、リクエストの権限部分（ホストおよびポート）がHostヘッダー（存在する場合）に提供されたものと厳密に一致するかどうかのチェックが行われていませんでした。これは以前のHTTP RFC（例えばRFC 2616）では強制されていませんでしたが、最新のRFC（9110および9112）では強制されています。この不一致は、以下のような脆弱性を引き起こす可能性があります。 * URIの構築（例えばリダイレクトにおいて—ログインページで典型的です） * 仮想ホストの選択 * リバースプロキシの動作異常 * 誤解を招くログ記録 * その他の問題 最新のRFCでは、リクエストの権限部分とHostヘッダーが一致しなければならないと要求しているため、Jettyはこの不変条件を強制すべきです。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • jenkins.src as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
  • ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services
  • jetty-server as a component of Red Hat AMQ Broker 7
  • jetty-server as a component of Red Hat build of Apache Camel - HawtIO 4
  • jetty-server as a component of Red Hat build of Apache Camel for Spring Boot 4
  • jetty-server as a component of Red Hat build of Apicurio Registry 3
  • jetty-server as a component of Red Hat build of Debezium 3
  • jetty-server as a component of Red Hat Data Grid 8
  • maven-site-plugin-javadoc as a component of Red Hat Enterprise Linux 7
  • maven-site-plugin.src as a component of Red Hat Enterprise Linux 7
  • resteasy-javadoc (pki-core:10.6) as a component of Red Hat Enterprise Linux 8
  • resteasy-javadoc (pki-deps:10.6) as a component of Red Hat Enterprise Linux 8
  • resteasy.src (pki-core:10.6) as a component of Red Hat Enterprise Linux 8
  • resteasy.src (pki-deps:10.6) as a component of Red Hat Enterprise Linux 8
  • resteasy (pki-core:10.6) as a component of Red Hat Enterprise Linux 8
  • resteasy (pki-deps:10.6) as a component of Red Hat Enterprise Linux 8
  • jmc as a component of Red Hat Enterprise Linux 9
  • jmc.src as a component of Red Hat Enterprise Linux 9
  • pki-resteasy as a component of Red Hat Enterprise Linux 9
  • pki-resteasy-client as a component of Red Hat Enterprise Linux 9
  • pki-resteasy-core as a component of Red Hat Enterprise Linux 9
  • pki-resteasy-jackson2-provider as a component of Red Hat Enterprise Linux 9
  • pki-resteasy-servlet-initializer as a component of Red Hat Enterprise Linux 9
  • jetty-server as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack
  • offline-knowledge-portal/rhokp-rhel9 as a component of Red Hat Offline Knowledge Portal
  • rhoai/odh-spark-operator-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • rhoai/odh-th06-cpu-torch291-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • rhoai/odh-th06-cuda130-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • and 12 more
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 14 Jul 2026 · Last source change 14 Jul 2026, 12:20 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-43646
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-43646↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-6790 · cve.blacktree.nl