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

Denial of Service in Python Protobuf

Python · Protobuf

8.2HighCVSS 4.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, 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.72% 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 Python Protobuf 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: Within 30 daysRemediation target: Within 180 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.

5 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 · sourceprotobufVendor fix publishedDebian records a fixed source-package version for this release.3.21.12-11+deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceprotobufVendor fix publishedDebian records a fixed source-package version for this release.3.21.12-3+deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceprotobufVendor fix publishedDebian records a fixed source-package version for this release.3.21.12-16Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceprotobufVendor fix publishedDebian records a fixed source-package version for this release.3.21.12-16Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveprotobufVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.21.12-8.2ubuntu0.3Canonical 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
PyPIprotobufECOSYSTEM: introduced 6.30.0rc1; fixed 6.33.56.33.5OSV record ↗aggregator derived · 10 Sep 2026
PyPIprotobufECOSYSTEM: introduced 0; fixed 5.29.65.29.6OSV record ↗aggregator derived · 10 Sep 2026
pipprotobuf>= 6.30.0rc1, <= 6.33.46.33.5GitHub advisory ↗github reviewed aggregator · 5 Feb 2026
pipprotobuf< 5.29.65.29.6GitHub advisory ↗github reviewed aggregator · 5 Feb 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-0994 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypython: protobuf: Protobuf: Denial of Service due to recursion depth bypass
448 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • python3.12-protobuf-0:5.29.6-1.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-0:5.29.6-1.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-0:5.29.6-1.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-0:5.29.6-1.el8ap.src as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-0:5.29.6-1.el8ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debuginfo-0:5.29.6-1.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debuginfo-0:5.29.6-1.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debuginfo-0:5.29.6-1.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debuginfo-0:5.29.6-1.el8ap.x86_64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debugsource-0:5.29.6-1.el8ap.aarch64 as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debugsource-0:5.29.6-1.el8ap.ppc64le as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
  • python3.12-protobuf-debugsource-0:5.29.6-1.el8ap.s390x as a component of Red Hat Ansible Automation Platform 2.5 for RHEL 8
Summary
A flaw was found in protobuf. A remote attacker can exploit this denial-of-service (DoS) vulnerability by supplying deeply nested `google.protobuf.Any` messages to the `google.protobuf.json_format.ParseDict()` function. This bypasses the intended recursion depth limit, leading to the exhaustion of Python’s recursion stack and causing a `RecursionError`, which results in a denial of service.
Remediation
For details on how to apply this update, refer to Ansible Automation Platform documentation.
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-4322

No EUVD known-exploited evidence

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

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
8.2 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

What

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

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 → Uncontrolled Recursion → 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
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-674 ↗

CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

Common Vulnerability Scoring System 4.0: 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.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SALowSubsequent-system availability: A successful attack can cause a limited loss.
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-674
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-4322Official EUVD mapping

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

Official EUVD record ↗
BSI · German · WID-SEC-2026-0480Red Hat Enterprise Linux (Python Protobuf): Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260128Security Bulletin 28 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Jan 2026, published on 28 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ERecord?id=CVE-2025-66168 Référence CVE CVE-2025-66199 https://www.cve.org/CVERecord?id=CVE-2025-66199 Référence CVE CVE-2025-66566 https://www.cve.org/CVERecord?id=CVE-2025-66566 Référence CVE CVE-2025-68160 https://www.cve.org/CVERecord?id=CVE-2025-68160 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-7338 https://www.cve.org/CVERecord?id=CVE-2025-7338 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2026-0636 https://www.cve.org/CVERecord?id=CVE-2026-0636 Référence CVE CVE-2026-0994 https://www.cve.org/CVERecord?id=CVE-2026-0994 Référence CVE CVE-2026-10536 https://www.cve.org/CVERecord?id=CVE-2026-10536 Référence CVE CVE-2026-11856 https://www.cve.org/CVERecord?id=CVE-2026-11856 Référence CVE CVE-2026-12143 https://www.cve.org/CVERecord?id=CVE-2026-12143 Référence CVE CVE-2026-12590 https://www.cve.org/CVERecord?id=CVE-2026-12590 Référence CVE CVE-2026-13149 https://www.cve.org/CVERecord?id=CVE-2026-13149 Référence CVE CVE-2026-13311 https://www.cve.org/CVERecord?id=CVE-2026-13311 Référence CVE CVE-2026-14446 https://www.cve.org/CVERecord?id=CVE-2026-14446 Référence CVE CVE-2026-14512 https://www.cve.org/CVERecord?id=C

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

ecord?id=CVE-2025-67735 Référence CVE CVE-2025-68160 https://www.cve.org/CVERecord?id=CVE-2025-68160 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-69418 https://www.cve.org/CVERecord?id=CVE-2025-69418 Référence CVE CVE-2025-69419 https://www.cve.org/CVERecord?id=CVE-2025-69419 Référence CVE CVE-2025-69420 https://www.cve.org/CVERecord?id=CVE-2025-69420 Référence CVE CVE-2025-69421 https://www.cve.org/CVERecord?id=CVE-2025-69421 Référence CVE CVE-2025-7962 https://www.cve.org/CVERecord?id=CVE-2025-7962 Référence CVE CVE-2026-0636 https://www.cve.org/CVERecord?id=CVE-2026-0636 Référence CVE CVE-2026-0994 https://www.cve.org/CVERecord?id=CVE-2026-0994 Référence CVE CVE-2026-10109 https://www.cve.org/CVERecord?id=CVE-2026-10109 Référence CVE CVE-2026-10845 https://www.cve.org/CVERecord?id=CVE-2026-10845 Référence CVE CVE-2026-11383 https://www.cve.org/CVERecord?id=CVE-2026-11383 Référence CVE CVE-2026-11536 https://www.cve.org/CVERecord?id=CVE-2026-11536 Référence CVE CVE-2026-11541 https://www.cve.org/CVERecord?id=CVE-2026-11541 Référence CVE CVE-2026-11594 https://www.cve.org/CVERecord?id=CVE-2026-11594 Référence CVE CVE-2026-11707 https://www.cve.org/CVERecord?id=CVE-2026-11707 Référence CVE CVE-2026-11806 https://www.cve.org/CVERecord?id=C

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

ord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-61723 https://www.cve.org/CVERecord?id=CVE-2025-61723 Référence CVE CVE-2025-61725 https://www.cve.org/CVERecord?id=CVE-2025-61725 Référence CVE CVE-2025-61726 https://www.cve.org/CVERecord?id=CVE-2025-61726 Référence CVE CVE-2025-61728 https://www.cve.org/CVERecord?id=CVE-2025-61728 Référence CVE CVE-2025-61730 https://www.cve.org/CVERecord?id=CVE-2025-61730 Référence CVE CVE-2025-6395 https://www.cve.org/CVERecord?id=CVE-2025-6395 Référence CVE CVE-2025-68121 https://www.cve.org/CVERecord?id=CVE-2025-68121 Référence CVE CVE-2026-0994 https://www.cve.org/CVERecord?id=CVE-2026-0994 Référence CVE CVE-2026-20202 https://www.cve.org/CVERecord?id=CVE-2026-20202 Référence CVE CVE-2026-20203 https://www.cve.org/CVERecord?id=CVE-2026-20203 Référence CVE CVE-2026-20204 https://www.cve.org/CVERecord?id=CVE-2026-20204 Référence CVE CVE-2026-20205 https://www.cve.org/CVERecord?id=CVE-2026-20205 Référence CVE CVE-2026-21226 https://www.cve.org/CVERecord?id=CVE-2026-21226 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Gestion détaillée du document le 16 avril 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À

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

.cve.org/CVERecord?id=CVE-2026-0861 Référence CVE CVE-2026-0865 https://www.cve.org/CVERecord?id=CVE-2026-0865 Référence CVE CVE-2026-0900 https://www.cve.org/CVERecord?id=CVE-2026-0900 Référence CVE CVE-2026-0902 https://www.cve.org/CVERecord?id=CVE-2026-0902 Référence CVE CVE-2026-0915 https://www.cve.org/CVERecord?id=CVE-2026-0915 Référence CVE CVE-2026-0988 https://www.cve.org/CVERecord?id=CVE-2026-0988 Référence CVE CVE-2026-0989 https://www.cve.org/CVERecord?id=CVE-2026-0989 Référence CVE CVE-2026-0990 https://www.cve.org/CVERecord?id=CVE-2026-0990 Référence CVE CVE-2026-0992 https://www.cve.org/CVERecord?id=CVE-2026-0992 Référence CVE CVE-2026-0994 https://www.cve.org/CVERecord?id=CVE-2026-0994 Référence CVE CVE-2026-1002 https://www.cve.org/CVERecord?id=CVE-2026-1002 Référence CVE CVE-2026-1484 https://www.cve.org/CVERecord?id=CVE-2026-1484 Référence CVE CVE-2026-1485 https://www.cve.org/CVERecord?id=CVE-2026-1485 Référence CVE CVE-2026-1489 https://www.cve.org/CVERecord?id=CVE-2026-1489 Référence CVE CVE-2026-2003 https://www.cve.org/CVERecord?id=CVE-2026-2003 Référence CVE CVE-2026-2004 https://www.cve.org/CVERecord?id=CVE-2026-2004 Référence CVE CVE-2026-2005 https://www.cve.org/CVERecord?id=CVE-2026-2005 Référence CVE CVE-2026-2006 https://www.cve.org/CVERecord?id=CVE-2026-2006 Ré

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-010778Googleのprotobufにおける再帰制御に関する脆弱性

Pythonのgoogle.protobuf.json_format.ParseDict()において、ネストされたgoogle.protobuf.Anyメッセージを解析する際にmax_recursion_depth制限を回避できるサービス拒否（DoS）脆弱性が存在します。内部のAny処理ロジックで再帰深度の計測が欠落しているため、攻撃者は意図された再帰制限を回避する深くネストされたAny構造を供給でき、最終的にPythonの再帰スタックを枯渇させ、その結果RecursionErrorを引き起こす可能性があります。

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.
Patch available
Affected
Protobuf: ≤ v33.4
Fixed
Action
For details on how to apply this update, refer to Ansible Automation Platform documentation.
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 23 Jan 2026 · Last source change 1 Sept 2026, 12:04 UTC · CWE-674 · Uncontrolled Recursion

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-4322
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:61627; removed vendor advisory: access.redhat.com/RHSA-2026:61629.
    Before
    patch: github.com/25239 · remediation: github.com/25239 · vendor advisory: access.redhat.com/RHSA-2026:61627 · 1 more references
    After
    patch: github.com/25239 · remediation: github.com/25239
    cve-coordination@google.com ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: access.redhat.com/RHSA-2026:61627; added vendor advisory: access.redhat.com/RHSA-2026:61629.
    Before
    patch: github.com/25239 · remediation: github.com/25239
    After
    patch: github.com/25239 · remediation: github.com/25239 · vendor advisory: access.redhat.com/RHSA-2026:61627 · 1 more references
    cve-coordination@google.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    <=v33.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    Protobuf: <=v33.4 · Fixed: RHSA-2026:3959: Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9
    CNA ↗
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-4322↗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-0994 · cve.blacktree.nl