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

CRMF/CMP password-MAC honours unbounded iteration count

Legion of the Bouncy Castle Inc. · BC-JAVA

6.9MediumCVSS 4.0
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 4 structured product or package states 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.42% 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 Legion of the Bouncy Castle Inc. BC-JAVA 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 4 structured product or package states 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 2 affected package states 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 · sourcebouncycastleAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebouncycastleAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebouncycastleVendor fix publishedDebian records a fixed source-package version for this release.1.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebouncycastleVendor fix publishedDebian records a fixed source-package version for this release.1.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsbouncycastleUnder 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
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-59647 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.bouncycastle/bcprov-jdk15on: org.bouncycastle/bcpkix-fips: Bouncy Castle for Java: Denial of Service via unbounded iteration in CRMF/CMP password-MAC
2 known affected

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

  • bcprov-jdk15on as a component of Red Hat JBoss Enterprise Application Platform 7
  • bcprov-jdk15on as a component of Red Hat Single Sign-On 7
Summary
A flaw was found in Bouncy Castle for Java. The Certificate Request Message Format (CRMF) and Certificate Management Protocol (CMP) password-based Message Authentication Code (MAC) implementation allows for an unbounded iteration count. A remote attacker can exploit this by sending a specially crafted request, leading to a denial of service (DoS) due to excessive resource consumption.
Remediation
Red Hat is not aware of a mitigation for this flaw other than updating the affected Bouncy Castle component to a fixed version (bc-java 1.85, LTS 2.73.12, or BC-FJA bcpkix-fips 1.0.12/2.0.12/2.1.12) once available for the affected product.
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-52027

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 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In Bouncy Castle for Java before 1.85, CRMF/CMP password-MAC honours unbounded iteration count. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X series) and 2.1.12 (2.1.X series).

What

In Bouncy Castle for Java before 1.85, CRMF/CMP password-MAC honours unbounded iteration count. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X series) and 2.1.12 (2.1.X series).

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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 Bouncy Castle for Java before 1.85, CRMF/CMP password-MAC honours unbounded iteration count. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcpkix-fips 1.0.12 (1.0.X series), 2.0.12 (2.0.X series) and 2.1.12 (2.1.X series).

Why

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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 → Allocation of Resources Without Limits or Throttling → 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-770 ↗

CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/U:Amber

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.ATNoneAttack requirements: No additional deployment or execution condition is required.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.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: 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-770
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2958IBM License Metric Tool: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2622Bouncy Castle: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Bouncy Castle ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

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

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

d?id=CVE-2026-58063 Référence CVE CVE-2026-58469 https://www.cve.org/CVERecord?id=CVE-2026-58469 Référence CVE CVE-2026-58471 https://www.cve.org/CVERecord?id=CVE-2026-58471 Référence CVE CVE-2026-58472 https://www.cve.org/CVERecord?id=CVE-2026-58472 Référence CVE CVE-2026-59638 https://www.cve.org/CVERecord?id=CVE-2026-59638 Référence CVE CVE-2026-59639 https://www.cve.org/CVERecord?id=CVE-2026-59639 Référence CVE CVE-2026-59642 https://www.cve.org/CVERecord?id=CVE-2026-59642 Référence CVE CVE-2026-59645 https://www.cve.org/CVERecord?id=CVE-2026-59645 Référence CVE CVE-2026-59646 https://www.cve.org/CVERecord?id=CVE-2026-59646 Référence CVE CVE-2026-59647 https://www.cve.org/CVERecord?id=CVE-2026-59647 Référence CVE CVE-2026-59648 https://www.cve.org/CVERecord?id=CVE-2026-59648 Référence CVE CVE-2026-59650 https://www.cve.org/CVERecord?id=CVE-2026-59650 Référence CVE CVE-2026-59651 https://www.cve.org/CVERecord?id=CVE-2026-59651 Référence CVE CVE-2026-59652 https://www.cve.org/CVERecord?id=CVE-2026-59652 Référence CVE CVE-2026-59843 https://www.cve.org/CVERecord?id=CVE-2026-59843 Référence CVE CVE-2026-59844 https://www.cve.org/CVERecord?id=CVE-2026-59844 Référence CVE CVE-2026-59845 https://www.cve.org/CVERecord?id=CVE-2026-59845 Référence CVE CVE-2026-59846 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-53669 Référence CVE CVE-2026-55602 https://www.cve.org/CVERecord?id=CVE-2026-55602 Référence CVE CVE-2026-55603 https://www.cve.org/CVERecord?id=CVE-2026-55603 Référence CVE CVE-2026-58059 https://www.cve.org/CVERecord?id=CVE-2026-58059 Référence CVE CVE-2026-58060 https://www.cve.org/CVERecord?id=CVE-2026-58060 Référence CVE CVE-2026-58061 https://www.cve.org/CVERecord?id=CVE-2026-58061 Référence CVE CVE-2026-58062 https://www.cve.org/CVERecord?id=CVE-2026-58062 Référence CVE CVE-2026-58063 https://www.cve.org/CVERecord?id=CVE-2026-58063 Référence CVE CVE-2026-59645 https://www.cve.org/CVERecord?id=CVE-2026-59645 Référence CVE CVE-2026-59647 https://www.cve.org/CVERecord?id=CVE-2026-59647 Référence CVE CVE-2026-59648 https://www.cve.org/CVERecord?id=CVE-2026-59648 Référence CVE CVE-2026-59650 https://www.cve.org/CVERecord?id=CVE-2026-59650 Référence CVE CVE-2026-59651 https://www.cve.org/CVERecord?id=CVE-2026-59651 Référence CVE CVE-2026-59652 https://www.cve.org/CVERecord?id=CVE-2026-59652 Référence CVE CVE-2026-59869 https://www.cve.org/CVERecord?id=CVE-2026-59869 Référence CVE CVE-2026-59878 https://www.cve.org/CVERecord?id=CVE-2026-59878 Référence CVE CVE-2026-60147 https://www.cve.org/CVERecord?id=CVE-2026-60147 Référence CVE CVE-2026-60589 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-58062 Référence CVE CVE-2026-58063 https://www.cve.org/CVERecord?id=CVE-2026-58063 Référence CVE CVE-2026-59083 https://www.cve.org/CVERecord?id=CVE-2026-59083 Référence CVE CVE-2026-59084 https://www.cve.org/CVERecord?id=CVE-2026-59084 Référence CVE CVE-2026-59295 https://www.cve.org/CVERecord?id=CVE-2026-59295 Référence CVE CVE-2026-59296 https://www.cve.org/CVERecord?id=CVE-2026-59296 Référence CVE CVE-2026-59639 https://www.cve.org/CVERecord?id=CVE-2026-59639 Référence CVE CVE-2026-59642 https://www.cve.org/CVERecord?id=CVE-2026-59642 Référence CVE CVE-2026-59645 https://www.cve.org/CVERecord?id=CVE-2026-59645 Référence CVE CVE-2026-59647 https://www.cve.org/CVERecord?id=CVE-2026-59647 Référence CVE CVE-2026-59648 https://www.cve.org/CVERecord?id=CVE-2026-59648 Référence CVE CVE-2026-59650 https://www.cve.org/CVERecord?id=CVE-2026-59650 Référence CVE CVE-2026-59651 https://www.cve.org/CVERecord?id=CVE-2026-59651 Référence CVE CVE-2026-59652 https://www.cve.org/CVERecord?id=CVE-2026-59652 Référence CVE CVE-2026-59869 https://www.cve.org/CVERecord?id=CVE-2026-59869 Référence CVE CVE-2026-59879 https://www.cve.org/CVERecord?id=CVE-2026-59879 Référence CVE CVE-2026-59880 https://www.cve.org/CVERecord?id=CVE-2026-59880 Référence CVE CVE-2026-59888 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030964Bouncy Castleのbc-java等の複数製品における制限またはスロットリング無しのリソースの割り当てに関する脆弱性

1.85より前のBouncy Castle for Javaでは、CRMF/CMPのパスワード-MACに無制限の繰り返し回数を許容する問題があります。この問題は、2.73.12より前のBouncy Castle for Java LTS、およびbcpkix-fips 1.0.12（1.0.Xシリーズ）、2.0.12（2.0.Xシリーズ）、2.1.12（2.1.Xシリーズ）より前のBouncy Castle for Java FIPS（BC-FJA）にも影響を及ぼします。

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
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.
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
Red Hat is not aware of a mitigation for this flaw other than updating the affected Bouncy Castle component to a fixed version (bc-java 1.85, LTS 2.73.12, or BC-FJA bcpkix-fips 1.0.12/2.0.12/2.1.12) once available for the affected product.
04

Evidence and provenance

Published 3 Aug 2026 · Last source change 3 Aug 2026, 13:34 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling

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-52027
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    resteasy-javadoc (pki-deps: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-deps:10.6) as a component of Red Hat Enterprise Linux 8; 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; bcprov-jdk15on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk15on as a component of Red Hat Single Sign-On 7
    After
    bcprov-jdk15on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk15on as a component of Red Hat Single Sign-On 7
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    bcprov-jdk15on as a component of Red Hat AMQ Clients; 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; 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; bcprov-jdk15on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk15on as a component of Red Hat Single Sign-On 7
    After
    resteasy-javadoc (pki-deps: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-deps:10.6) as a component of Red Hat Enterprise Linux 8; 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; bcprov-jdk15on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk15on as a component of Red Hat Single Sign-On 7
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/c99d6427d6818d04165b07b45dfda96f2b384c53; added remediation: github.com/c99d6427d6818d04165b07b45dfda96f2b384c53.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/c99d6427d6818d04165b07b45dfda96f2b384c53 · remediation: github.com/c99d6427d6818d04165b07b45dfda96f2b384c53
    github.com ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.85; 2.73.0 < 2.73.12; 1.0.0 < 1.0.12; 2.0.0 < 2.0.12; 2.1.0 < 2.1.12 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 1.85; 2.73.0 < 2.73.12; 1.0.0 < 1.0.12; 2.0.0 < 2.0.12; 2.1.0 < 2.1.12 · 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.
    CNA ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
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-52027↗Vendor CSAF · Red Hat Product Security↗Patch or update reference↗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-59647 · cve.blacktree.nl