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

Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

ISC · BIND 9

6.5MediumCVSS 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.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.24% 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 ISC BIND 9 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

Alpine, 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
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
Alpine v3.23v3.23 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.20.29-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainbindVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.20.29-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.29-1~deb13u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebind9Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.29-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebind9Vendor fix publishedDebian records a fixed source-package version for this release.1:9.20.29-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivebind9Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveisc-dhcpUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 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-19033 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybind: BIND: Unauthorized zone content updates via unauthenticated IXFR deltas
75 known affected

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

  • bind as a component of Red Hat Enterprise Linux 10
  • bind-chroot as a component of Red Hat Enterprise Linux 10
  • bind-devel as a component of Red Hat Enterprise Linux 10
  • bind-dnssec-utils as a component of Red Hat Enterprise Linux 10
  • bind-doc as a component of Red Hat Enterprise Linux 10
  • bind-libs as a component of Red Hat Enterprise Linux 10
  • bind-license as a component of Red Hat Enterprise Linux 10
  • bind-utils as a component of Red Hat Enterprise Linux 10
  • bind.src as a component of Red Hat Enterprise Linux 10
  • bind as a component of Red Hat Enterprise Linux 7
  • bind-chroot as a component of Red Hat Enterprise Linux 7
  • bind-devel as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in bind. A remote attacker without a valid TSIG (Transaction Signature) can send unauthorized zone contents to a secondary server during a multi-message TCP IXFR (Incremental Zone Transfer). The `named` process may apply this unauthenticated data before the TSIG signature is verified. If the signature never arrives, `named` does not revert to its previous state, leading to the serving of unauthorized zone data and compromising information integrity.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
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-80781

No EUVD known-exploited evidence

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

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
6.5 · CVSS 3.1
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

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

What

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Why

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

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

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Why

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

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 → Acceptance of Extraneous Untrusted Data With Trusted Data → 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
High: exploitation depends on specific conditions
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-349 ↗

CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data. The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

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:H/PR:N/UI:N/S:U/C:N/I:H/A:L

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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: 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-349
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-80781Official EUVD mapping

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3420Internet Systems Consortium BIND: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um Daten zu manipulieren, Sicherheitsmaßnahmen zu umgehen oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260923Security Bulletin 23 Sep 2026

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

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 16 Sept 2026 · Last source change 17 Sept 2026, 17:36 UTC · CWE-349 · Acceptance of Extraneous Untrusted Data With Trusted Data

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-09-17
European sourceENISA EUVD · EUVD-2026-80781
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting 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 from remediation: access.redhat.com/CVE-2026-19033 to remediation: access.redhat.com/CVE-2026-19033.
    Before
    remediation: access.redhat.com/CVE-2026-19033
    After
    remediation: access.redhat.com/CVE-2026-19033
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    bind as a component of Red Hat Enterprise Linux 10; bind-chroot as a component of Red Hat Enterprise Linux 10; bind-devel as a component of Red Hat Enterprise Linux 10; bind-dnssec-utils as a component of Red Hat Enterprise Linux 10; bind-doc as a component of Red Hat Enterprise Linux 10; bind-libs as a component of Red Hat Enterprise Linux 10; bind-license as a component of Red Hat Enterprise Linux 10; bind-utils as a component of Red Hat Enterprise Linux 10; bind.src as a component of Red Hat Enterprise Linux 10; bind as a component of Red Hat Enterprise Linux 7; bind-chroot as a component of Red Hat Enterprise Linux 7; bind-devel as a component of Red Hat Enterprise Linux 7; bind-export-devel as a component of Red Hat Enterprise Linux 7; bind-export-libs as a component of Red Hat Enterprise Linux 7; bind-libs as a component of Red Hat Enterprise Linux 7; bind-libs-lite as a component of Red Hat Enterprise Linux 7; bind-license as a component of Red Hat Enterprise Linux 7; bind-lite-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11 as a component of Red Hat Enterprise Linux 7; bind-pkcs11-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11-libs as a component of Red Hat Enterprise Linux 7; bind-pkcs11-utils as a component of Red Hat Enterprise Linux 7; bind-sdb as a component of Red Hat Enterprise Linux 7; bind-sdb-chroot as a component of Red Hat Enterprise Linux 7; bind-utils as a component of Red Hat Enterprise Linux 7; bind.src as a component of Red Hat Enterprise Linux 7; bind as a component of Red Hat Enterprise Linux 8; bind-chroot as a component of Red Hat Enterprise Linux 8; bind-devel as a component of Red Hat Enterprise Linux 8; bind-export-devel as a component of Red Hat Enterprise Linux 8; and 46 more
    After
    bind as a component of Red Hat Enterprise Linux 10; bind-chroot as a component of Red Hat Enterprise Linux 10; bind-devel as a component of Red Hat Enterprise Linux 10; bind-dnssec-utils as a component of Red Hat Enterprise Linux 10; bind-doc as a component of Red Hat Enterprise Linux 10; bind-libs as a component of Red Hat Enterprise Linux 10; bind-license as a component of Red Hat Enterprise Linux 10; bind-utils as a component of Red Hat Enterprise Linux 10; bind.src as a component of Red Hat Enterprise Linux 10; bind as a component of Red Hat Enterprise Linux 7; bind-chroot as a component of Red Hat Enterprise Linux 7; bind-devel as a component of Red Hat Enterprise Linux 7; bind-export-devel as a component of Red Hat Enterprise Linux 7; bind-export-libs as a component of Red Hat Enterprise Linux 7; bind-libs as a component of Red Hat Enterprise Linux 7; bind-libs-lite as a component of Red Hat Enterprise Linux 7; bind-license as a component of Red Hat Enterprise Linux 7; bind-lite-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11 as a component of Red Hat Enterprise Linux 7; bind-pkcs11-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11-libs as a component of Red Hat Enterprise Linux 7; bind-pkcs11-utils as a component of Red Hat Enterprise Linux 7; bind-sdb as a component of Red Hat Enterprise Linux 7; bind-sdb-chroot as a component of Red Hat Enterprise Linux 7; bind-utils as a component of Red Hat Enterprise Linux 7; bind.src as a component of Red Hat Enterprise Linux 7; bind as a component of Red Hat Enterprise Linux 8; bind-chroot as a component of Red Hat Enterprise Linux 8; bind-devel as a component of Red Hat Enterprise Linux 8; bind-export-devel as a component of Red Hat Enterprise Linux 8; and 45 more · Fixed: bind-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-0:9.20.29-0.1.hum1@src as a component of Red Hat Hardened Images; bind-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; bind-chroot-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-chroot-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; bind-devel-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-devel-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; bind-dnssec-utils-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-dnssec-utils-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; bind-doc-0:9.20.29-0.1.hum1@noarch@public-hummingbird-aarch64-rpms as a component of Red Hat Hardened Images; bind-doc-0:9.20.29-0.1.hum1@noarch@public-hummingbird-x86_64-rpms as a component of Red Hat Hardened Images; bind-libs-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-libs-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images; bind-utils-0:9.20.29-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; bind-utils-0:9.20.29-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-19033 to remediation: access.redhat.com/CVE-2026-19033.
    Before
    remediation: access.redhat.com/CVE-2026-19033
    After
    remediation: access.redhat.com/CVE-2026-19033
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
    After
    bind as a component of Red Hat Enterprise Linux 10; bind-chroot as a component of Red Hat Enterprise Linux 10; bind-devel as a component of Red Hat Enterprise Linux 10; bind-dnssec-utils as a component of Red Hat Enterprise Linux 10; bind-doc as a component of Red Hat Enterprise Linux 10; bind-libs as a component of Red Hat Enterprise Linux 10; bind-license as a component of Red Hat Enterprise Linux 10; bind-utils as a component of Red Hat Enterprise Linux 10; bind.src as a component of Red Hat Enterprise Linux 10; bind as a component of Red Hat Enterprise Linux 7; bind-chroot as a component of Red Hat Enterprise Linux 7; bind-devel as a component of Red Hat Enterprise Linux 7; bind-export-devel as a component of Red Hat Enterprise Linux 7; bind-export-libs as a component of Red Hat Enterprise Linux 7; bind-libs as a component of Red Hat Enterprise Linux 7; bind-libs-lite as a component of Red Hat Enterprise Linux 7; bind-license as a component of Red Hat Enterprise Linux 7; bind-lite-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11 as a component of Red Hat Enterprise Linux 7; bind-pkcs11-devel as a component of Red Hat Enterprise Linux 7; bind-pkcs11-libs as a component of Red Hat Enterprise Linux 7; bind-pkcs11-utils as a component of Red Hat Enterprise Linux 7; bind-sdb as a component of Red Hat Enterprise Linux 7; bind-sdb-chroot as a component of Red Hat Enterprise Linux 7; bind-utils as a component of Red Hat Enterprise Linux 7; bind.src as a component of Red Hat Enterprise Linux 7; bind as a component of Red Hat Enterprise Linux 8; bind-chroot as a component of Red Hat Enterprise Linux 8; bind-devel as a component of Red Hat Enterprise Linux 8; bind-export-devel as a component of Red Hat Enterprise Linux 8; and 46 more
    Red Hat Product Security ↗
  7. ENISA EUVD mappingEUVD-2026-80781 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-80781"}
    ENISA EUVD ↗
  8. Catalogue recordCVE added to the BlackTree catalogue.
    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-80781↗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-19033 · cve.blacktree.nl