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

undici is vulnerable to CRLF Injection via upgrade option

undici · undici

Official source article: GitHub GHSA-4992-7RV2-5PVQ ↗. Check the applicable product and release in the original source.

4.6MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
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.
  • EPSS is 0.28% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • 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 undici undici and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

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.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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 · sourcenode-undiciAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenode-undiciNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenode-undiciVendor fix publishedDebian records a fixed source-package version for this release.7.24.5+dfsg+~cs3.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenode-undiciVendor fix publishedDebian records a fixed source-package version for this release.7.24.5+dfsg+~cs3.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-undiciUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 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
npmundici< 6.24.06.24.0GitHub advisory ↗upstream repository advisory · 13 Mar 2026
npmundici>= 7.0.0, < 7.24.07.24.0GitHub advisory ↗upstream repository advisory · 13 Mar 2026
npmundiciSEMVER: introduced 0; fixed 6.24.06.24.0OSV record ↗aggregator derived · 10 Sep 2026
npmundiciSEMVER: introduced 7.0.0; fixed 7.24.07.24.0OSV record ↗aggregator derived · 10 Sep 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-1527 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityundici: Undici: HTTP header injection and request smuggling vulnerability
59 known affected

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

  • io.cryostat-cryostat as a component of Cryostat 4
  • openshift-lightspeed/lightspeed-console-plugin-pf5-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-console-plugin-rhel9 as a component of OpenShift Lightspeed
  • openshift-pipelines/pipelines-console-plugin-rhel8 as a component of OpenShift Pipelines
  • openshift-pipelines/pipelines-console-plugin-rhel9 as a component of OpenShift Pipelines
  • rhdh/backstage-community-plugin-catalog-backend-module-scaffolder-relation-processor as a component of Red Hat Developer Hub
  • rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
  • nodejs as a component of Red Hat Enterprise Linux 10
  • nodejs-devel as a component of Red Hat Enterprise Linux 10
  • nodejs-docs as a component of Red Hat Enterprise Linux 10
  • nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
  • nodejs-libs as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in undici, a Node.js HTTP/1.1 client. This vulnerability allows a remote attacker to inject malicious data into HTTP headers or prematurely end HTTP requests by sending specially crafted input to the `upgrade` option of `client.request()`. This is possible because undici does not properly validate input for invalid header characters, which could lead to unauthorized information disclosure or bypassing of security controls.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-11701

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }

What

ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }

Why

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

ImpactWhen an application passes user-controlled input to the upgrade option of client.request(), an attacker can inject CRLF sequences (\r\n) to: * Inject arbitrary HTTP headers * Terminate the HTTP request prematurely and smuggle raw data to non-HTTP services (Redis, Memcached, Elasticsearch) The vulnerability exists because undici writes the upgrade value directly to the socket without validating for invalid header characters: // lib/dispatcher/client-h1.js:1121 if (upgrade) { header += `connection: upgrade\r\nupgrade: ${upgrade}\r\n` }

Why

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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 Neutralization of CRLF Sequences ('CRLF Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
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-93 ↗

CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection'). The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

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:L/UI:R/S:U/C:L/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.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.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.
NetworkCWE-93
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3621IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um Daten zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-3596IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um einen Cross-Site Scripting Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0933IBM App Connect Enterprise (Hono und Undici): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen oder andere nicht näher bezeichnete Angriffe durchzuführen.

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

d?id=CVE-2026-13697 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14620 https://www.cve.org/CVERecord?id=CVE-2026-14620 Référence CVE CVE-2026-14631 https://www.cve.org/CVERecord?id=CVE-2026-14631 Référence CVE CVE-2026-14643 https://www.cve.org/CVERecord?id=CVE-2026-14643 Référence CVE CVE-2026-14682 https://www.cve.org/CVERecord?id=CVE-2026-14682 Référence CVE CVE-2026-14802 https://www.cve.org/CVERecord?id=CVE-2026-14802 Référence CVE CVE-2026-15055 https://www.cve.org/CVERecord?id=CVE-2026-15055 Référence CVE CVE-2026-15157 https://www.cve.org/CVERecord?id=CVE-2026-15157 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-16221 https://www.cve.org/CVERecord?id=CVE-2026-16221 Référence CVE CVE-2026-16243 https://www.cve.org/CVERecord?id=CVE-2026-16243 Référence CVE CVE-2026-16439 https://www.cve.org/CVERecord?id=CVE-2026-16439 Référence CVE CVE-2026-16440 https://www.cve.org/CVERecord?id=CVE-2026-16440 Référence CVE CVE-2026-16441 https://www.cve.org/CVERecord?id=CVE-2026-16441 Référence CVE CVE-2026-16728 https://www.cve.org/CVERecord?id=CVE-2026-16728 Référence CVE CVE-2026-16729 https://www.cve.org/CVERecord?id=CVE-2026-16729 Référence CVE CVE-2026-18149 https://www.cve.org/CVERecord?id=C

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

ERecord?id=CVE-2025-58181 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-66030 https://www.cve.org/CVERecord?id=CVE-2025-66030 Référence CVE CVE-2025-66031 https://www.cve.org/CVERecord?id=CVE-2025-66031 Référence CVE CVE-2025-66035 https://www.cve.org/CVERecord?id=CVE-2025-66035 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-1525 https://www.cve.org/CVERecord?id=CVE-2026-1525 Référence CVE CVE-2026-1526 https://www.cve.org/CVERecord?id=CVE-2026-1526 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-1528 https://www.cve.org/CVERecord?id=CVE-2026-1528 Référence CVE CVE-2026-22007 https://www.cve.org/CVERecord?id=CVE-2026-22007 Référence CVE CVE-2026-22013 https://www.cve.org/CVERecord?id=CVE-2026-22013 Référence CVE CVE-2026-22016 https://www.cve.org/CVERecord?id=CVE-2026-22016 Référence CVE CVE-2026-22018 https://www.cve.org/CVERecord?id=CVE-2026-22018 Référence CVE CVE-2026-22021 https://www.cve.org/CVERecord?id=CVE-2026-22021 Référence CVE CVE-2026-22036 https://www.cve.org/CVERecord?id=CVE-2026-22036 Référence CVE CVE-2026-2229 https://www.cve.org/CVERecord?id=CVE-

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

e.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-69277 https://www.cve.org/CVERecord?id=CVE-2025-69277 Référence CVE CVE-2025-7339 https://www.cve.org/CVERecord?id=CVE-2025-7339 Référence CVE CVE-2026-0846 https://www.cve.org/CVERecord?id=CVE-2026-0846 Référence CVE CVE-2026-0847 https://www.cve.org/CVERecord?id=CVE-2026-0847 Référence CVE CVE-2026-0848 https://www.cve.org/CVERecord?id=CVE-2026-0848 Référence CVE CVE-2026-1519 https://www.cve.org/CVERecord?id=CVE-2026-1519 Référence CVE CVE-2026-1525 https://www.cve.org/CVERecord?id=CVE-2026-1525 Référence CVE CVE-2026-1526 https://www.cve.org/CVERecord?id=CVE-2026-1526 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-1528 https://www.cve.org/CVERecord?id=CVE-2026-1528 Référence CVE CVE-2026-21441 https://www.cve.org/CVERecord?id=CVE-2026-21441 Référence CVE CVE-2026-21860 https://www.cve.org/CVERecord?id=CVE-2026-21860 Référence CVE CVE-2026-22007 https://www.cve.org/CVERecord?id=CVE-2026-22007 Référence CVE CVE-2026-22008 https://www.cve.org/CVERecord?id=CVE-2026-22008 Référence CVE CVE-2026-22013 https://www.cve.org/CVERecord?id=CVE-2026-22013 Référence CVE CVE-2026-22016 https://www.cve.org/CVERecord?id=CVE-2026-22016 Référence CVE CVE-2026-22018 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0500Multiples vulnérabilités dans VMware Tanzu

cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2025-7962 https://www.cve.org/CVERecord?id=CVE-2025-7962 Référence CVE CVE-2025-8885 https://www.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-9624 https://www.cve.org/CVERecord?id=CVE-2025-9624 Référence CVE CVE-2026-1225 https://www.cve.org/CVERecord?id=CVE-2026-1225 Référence CVE CVE-2026-1525 https://www.cve.org/CVERecord?id=CVE-2026-1525 Référence CVE CVE-2026-1526 https://www.cve.org/CVERecord?id=CVE-2026-1526 Référence CVE CVE-2026-1527 https://www.cve.org/CVERecord?id=CVE-2026-1527 Référence CVE CVE-2026-22036 https://www.cve.org/CVERecord?id=CVE-2026-22036 Référence CVE CVE-2026-2229 https://www.cve.org/CVERecord?id=CVE-2026-2229 Référence CVE CVE-2026-22732 https://www.cve.org/CVERecord?id=CVE-2026-22732 Référence CVE CVE-2026-22735 https://www.cve.org/CVERecord?id=CVE-2026-22735 Référence CVE CVE-2026-22737 https://www.cve.org/CVERecord?id=CVE-2026-22737 Référence CVE CVE-2026-2332 https://www.cve.org/CVERecord?id=CVE-2026-2332 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-026930Node.js FoundationのundiciにおけるCRLF インジェクションの脆弱性

undici は、HTTP/1.1 ディスパッチャーで Content-Type ヘッダーとして使用する前に、ダックタイプのブロブに似たリクエストボディの type プロパティを検証しません。undici の 6.28.0 より前のバージョン、7.0.0 から 7.29.0 より前のバージョン、および 8.0.0 から 8.9.0 より前のバージョンでは、手作りのブロブに似たボディ（request、stream、pipeline、または dispatch 経由）を渡し、その type が信頼できない入力から派生しているアプリケーションは、攻撃者が CRLF シーケンスを注入して任意の HTTP ヘッダーを追加し、アップストリームを通過する第 2 のリクエストを密輸できる可能性があります。ネイティブの Blob オブジェクトは、そのコンストラクターが type から CRLF を除去するため安全であり、fetch はヘッダーを検証するため影響を受けませんが、ユーザー入力からダックタイプのブロブ形状を構築するエコシステムのライブラリは脆弱な経路に到達する可能性があります。これは、CVE-2022-35948 および CVE-2026-1527 と同じ欠陥クラスに属し、以前の修正ではカバーされなかったヘッダーシンクに関する問題です。この問題は undici の 6.28.0、7.29.0、および 8.9.0 で修正されています。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-008150Node.js FoundationのundiciにおけるCRLF インジェクションの脆弱性

アプリケーションがユーザー制御の入力をclient.request()のupgradeオプションに渡すと、攻撃者はCRLFシーケンス（\r\n）を注入して任意のHTTPヘッダーを挿入したり、HTTPリクエストを早期に終了させたりして、生のデータを非HTTPサービス（Redis、Memcached、Elasticsearch）にこっそり送信する可能性があります。この脆弱性は、undiciがupgradeの値を無効なヘッダー文字の検証なしに直接ソケットに書き込むために存在しています。

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 availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 12 Mar 2026 · Last source change 13 Mar 2026, 18:06 UTC · CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')

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-11701
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
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-11701↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-4992-7RV2-5PVQ↗Vendor advisory↗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-1527 · cve.blacktree.nl