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

Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Incorrect handling of TLSv1.3 KeyUpdate can be exploited to cause DoS via OOM

Apache Software Foundation · Apache ActiveMQ Client

7.5HighCVSS 3.1
Recommended action
Within 7 days

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

Fix not verified
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 1.06% for the current model date.

Compensating controls

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

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache ActiveMQ Client and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: 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.

4 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 · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceactivemqAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveactivemqUnder 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 ranges16 source-attributed ranges

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

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.activemq:activemq-allECOSYSTEM: introduced 0; fixed 5.19.45.19.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-allECOSYSTEM: introduced 6.0.0; fixed 6.2.46.2.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 0; fixed 5.19.45.19.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 6.0.0; fixed 6.2.46.2.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-clientECOSYSTEM: introduced 0; fixed 5.19.45.19.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-clientECOSYSTEM: introduced 6.0.0; fixed 6.2.46.2.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 0; fixed 5.19.45.19.4OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 6.0.0; fixed 6.2.46.2.4OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.apache.activemq:activemq-all< 5.19.45.19.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:activemq-all>= 6.0.0, < 6.2.46.2.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:activemq-broker< 5.19.45.19.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:activemq-broker>= 6.0.0, < 6.2.46.2.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:activemq-client< 5.19.45.19.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:activemq-client>= 6.0.0, < 6.2.46.2.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:apache-activemq< 5.19.45.19.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
mavenorg.apache.activemq:apache-activemq>= 6.0.0, < 6.2.46.2.4GitHub advisory ↗github reviewed aggregator · 10 Apr 2026
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-21362

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 actionWithin 7 days

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

Fix not verified
01

What, why and how

Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ. ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS. Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.

What

Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ. ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS. Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Denial of Service via Out of Memory vulnerability in Apache ActiveMQ Client, Apache ActiveMQ Broker, Apache ActiveMQ. ActiveMQ NIO SSL transports do not correctly handle TLSv1.3 handshake KeyUpdates triggered by clients. This makes it possible for a client to rapidly trigger updates which causes the broker to exhaust all its memory in the SSL engine leading to DoS. Note: TLS versions before TLSv1.3 (such as TLSv1.2) are broken but are not vulnerable to OOM. Previous TLS versions require a full handshake renegotiation which causes a connection to hang but not OOM. This is fixed as well. This issue affects Apache ActiveMQ Client: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ Broker: before 5.19.4, from 6.0.0 before 6.2.4; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.4. Users are recommended to upgrade to version 6.2.4 or 5.19.5, which fixes the issue.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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 Resource Consumption → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major 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.
NetworkUnauthenticatedDenial of serviceCWE-400
A

Official authority intelligence

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

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

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Sicherheitsvorkehrungen zu umgehen, 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 beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1608Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye und Jira): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um einen Cross-Site Scripting Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-1040Apache ActiveMQ: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ ausnutzen, um einen Denial of Service Angriff durchzuführen oder um nicht näher spezifizierte Auswirkungen zu verursachen

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026

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

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

ecord?id=CVE-2026-34518 Référence CVE CVE-2026-34519 https://www.cve.org/CVERecord?id=CVE-2026-34519 Référence CVE CVE-2026-34520 https://www.cve.org/CVERecord?id=CVE-2026-34520 Référence CVE CVE-2026-34525 https://www.cve.org/CVERecord?id=CVE-2026-34525 Référence CVE CVE-2026-34591 https://www.cve.org/CVERecord?id=CVE-2026-34591 Référence CVE CVE-2026-34993 https://www.cve.org/CVERecord?id=CVE-2026-34993 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3833 https://www.cve.org/CVERecord?id=CVE-2026-3833 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-39824 https://www.cve.org/CVERecord?id=CVE-2026-39824 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40046 https://www.cve.org/CVERecord?id=CVE-2026-40046 Référence CVE CVE-2026-40186 https://www.cve.org/CVERecord?id=CVE-2026-40186 Référence CVE CVE-2026-40347 https://www.cve.org/CVERecord?id=CVE-2026-40347 Référence CVE CVE-2026-40466 https://www.cve.org/CVERecord?id=CVE-2026-40466 Référence CVE CVE-2026-40895 https://www.cve.org/CVERecord?id=CVE-2026-40895 Référence CVE CVE-2026-41043 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-34481 https://www.cve.org/CVERecord?id=CVE-2026-34481 Référence CVE CVE-2026-34483 https://www.cve.org/CVERecord?id=CVE-2026-34483 Référence CVE CVE-2026-34487 https://www.cve.org/CVERecord?id=CVE-2026-34487 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=CVE-2026-3449 Référence CVE CVE-2026-34500 https://www.cve.org/CVERecord?id=CVE-2026-34500 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=CVE-2026-35554 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-39821 https://www.cve.org/CVERecord?id=CVE-2026-39821 Référence CVE CVE-2026-39827 https://www.cve.org/CVERecord?id=CVE-2026-39827 Référence CVE CVE-2026-39828 https://www.cve.org/CVERecord?id=CVE-2026-39828 Référence CVE CVE-2026-39829 https://www.cve.org/CVERecord?id=CVE-2026-39829 Référence CVE CVE-2026-39830 https://www.cve.org/CVERecord?id=CVE-2026-39830 Référence CVE CVE-2026-39831 https://www.cve.org/CVERecord?id=CVE-2026-39831 Référence CVE CVE-2026-39832 https://www.cve.org/CVERecord?id=CVE-2026-39832 Référence CVE CVE-2026-39833 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-34077 Référence CVE CVE-2026-34180 https://www.cve.org/CVERecord?id=CVE-2026-34180 Référence CVE CVE-2026-34182 https://www.cve.org/CVERecord?id=CVE-2026-34182 Référence CVE CVE-2026-34197 https://www.cve.org/CVERecord?id=CVE-2026-34197 Référence CVE CVE-2026-34483 https://www.cve.org/CVERecord?id=CVE-2026-34483 Référence CVE CVE-2026-34487 https://www.cve.org/CVERecord?id=CVE-2026-34487 Référence CVE CVE-2026-34500 https://www.cve.org/CVERecord?id=CVE-2026-34500 Référence CVE CVE-2026-34993 https://www.cve.org/CVERecord?id=CVE-2026-34993 Référence CVE CVE-2026-35554 https://www.cve.org/CVERecord?id=CVE-2026-35554 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-40046 https://www.cve.org/CVERecord?id=CVE-2026-40046 Référence CVE CVE-2026-40181 https://www.cve.org/CVERecord?id=CVE-2026-40181 Référence CVE CVE-2026-40198 https://www.cve.org/CVERecord?id=CVE-2026-40198 Référence CVE CVE-2026-40199 https://www.cve.org/CVERecord?id=CVE-2026-40199 Référence CVE CVE-2026-4176 https://www.cve.org/CVERecord?id=CVE-2026-4176 Référence CVE CVE-2026-41841 https://www.cve.org/CVERecord?id=CVE-2026-41841 Référence CVE CVE-2026-41842 https://www.cve.org/CVERecord?id=CVE-2026-41842 Référence CVE CVE-2026-41843 https://www.cve.org/CVERecord?id=CV

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

ecord?id=CVE-2026-33814 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-34077 https://www.cve.org/CVERecord?id=CVE-2026-34077 Référence CVE CVE-2026-34268 https://www.cve.org/CVERecord?id=CVE-2026-34268 Référence CVE CVE-2026-34282 https://www.cve.org/CVERecord?id=CVE-2026-34282 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=CVE-2026-3449 Référence CVE CVE-2026-3520 https://www.cve.org/CVERecord?id=CVE-2026-3520 Référence CVE CVE-2026-35536 https://www.cve.org/CVERecord?id=CVE-2026-35536 Référence CVE CVE-2026-39304 https://www.cve.org/CVERecord?id=CVE-2026-39304 Référence CVE CVE-2026-39821 https://www.cve.org/CVERecord?id=CVE-2026-39821 Référence CVE CVE-2026-39827 https://www.cve.org/CVERecord?id=CVE-2026-39827 Référence CVE CVE-2026-39828 https://www.cve.org/CVERecord?id=CVE-2026-39828 Référence CVE CVE-2026-39829 https://www.cve.org/CVERecord?id=CVE-2026-39829 Référence CVE CVE-2026-39830 https://www.cve.org/CVERecord?id=CVE-2026-39830 Référence CVE CVE-2026-39831 https://www.cve.org/CVERecord?id=CVE-2026-39831 Référence CVE CVE-2026-39832 https://www.cve.org/CVERecord?id=CVE-2026-39832 Référence CVE CVE-2026-39833 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014242Apache Software FoundationのApache ActiveMQ等の複数製品におけるリソースの枯渇に関する脆弱性

Apache ActiveMQ Client、Apache ActiveMQ Broker、およびApache ActiveMQにおけるメモリ不足によるサービス拒否（DoS）脆弱性です。ActiveMQのNIO SSLトランスポートは、クライアントによってトリガーされるTLSv1.3ハンドシェイクのKeyUpdateを正しく処理しません。これにより、クライアントが高速で連続的にアップデートをトリガーし、SSLエンジン内のメモリを枯渇させてDoSを引き起こす可能性があります。注意として、TLSv1.3より以前のTLSバージョン（例：TLSv1.2）は問題がありますが、OOM脆弱性は存在しません。以前のTLSバージョンでは完全なハンドシェイクの再ネゴシエーションが必要であり、接続がハングすることはありますがOOMは発生しません。この問題は既に修正されています。影響を受けるバージョンは、Apache ActiveMQ Clientの5.19.4未満および6.0.0から6.2.4未満、Apache ActiveMQ Brokerの5.19.4未満および6.0.0から6.2.4未満、Apache ActiveMQの5.19.4未満および6.0.0から6.2.4未満です。ユーザーは、この問題を修正したバージョン6.2.4または5.19.5へアップグレードすることを推奨します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • Apache ActiveMQ Client: < 5.19.4, 6.0.0 < 6.2.4
  • Apache ActiveMQ Broker: < 5.19.4, 6.0.0 < 6.2.4
  • Apache ActiveMQ All: < 5.19.4, 6.0.0 < 6.2.4
  • Apache ActiveMQ: < 5.19.4, 6.0.0 < 6.2.4
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 10 Apr 2026 · Last source change 15 Jul 2026, 01:02 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
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-21362
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-21362↗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-39304 · cve.blacktree.nl