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

Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Remote Code Execution via Jolokia addNetworkConnector

Apache Software Foundation · Apache ActiveMQ Broker

8.1HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 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 severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.66% 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 Apache Software Foundation Apache ActiveMQ Broker 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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 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.

4 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 3 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 · 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 ranges12 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.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-allECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 0; fixed 5.19.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:activemq-brokerECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 0; fixed 5.19.75.19.7OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.apache.activemq:apache-activemqECOSYSTEM: introduced 6.0.0; fixed 6.2.66.2.6OSV record ↗aggregator derived · 10 Sep 2026
mavenorg.apache.activemq:activemq-all< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-all>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-broker< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:activemq-broker>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:apache-activemq< 5.19.75.19.7GitHub advisory ↗github reviewed aggregator · 9 Jul 2026
mavenorg.apache.activemq:apache-activemq>= 6.0.0, < 6.2.66.2.6GitHub advisory ↗github reviewed aggregator · 9 Jul 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-42588 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.apache.activemq/activemq-broker: org.apache.activemq/activemq-all: org.apache.activemq/apache-activemq: Apache ActiveMQ: Arbitrary code execution via improper input validation in Jolokia JMX-HTTP bridge
2 known affected

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

  • activemq-all as a component of Red Hat Fuse 7
  • activemq-broker as a component of Red Hat Fuse 7
Summary
A flaw was found in Apache ActiveMQ. An authenticated attacker can exploit an improper input validation vulnerability in the Jolokia JMX-HTTP bridge. By crafting a malicious discovery URI, the attacker can trigger the VM transport's brokerConfig parameter to load a Spring XML application context. This allows for arbitrary code execution on the broker's Java Virtual Machine (JVM).
Remediation
Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
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-33577

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 3 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

Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter using the "masterslave:// " URL which can allow loading a Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.

What

Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter using the "masterslave:// " URL which can allow loading a Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ. Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter using the "masterslave:// " URL which can allow loading a Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6. Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
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-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkRemote code executionCWE-20
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-2460Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

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

Ein Angreifer kann mehrere Schwachstellen in Apache ActiveMQ ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen, Informationen offenzulegen, seine Rechte zu erweitern, Daten zu manipulieren und Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260603Security Bulletin 3 Jun 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 3 Jun 2026, published on 3 June 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

d?id=CVE-2026-42042 Référence CVE CVE-2026-42043 https://www.cve.org/CVERecord?id=CVE-2026-42043 Référence CVE CVE-2026-42044 https://www.cve.org/CVERecord?id=CVE-2026-42044 Référence CVE CVE-2026-42198 https://www.cve.org/CVERecord?id=CVE-2026-42198 Référence CVE CVE-2026-42253 https://www.cve.org/CVERecord?id=CVE-2026-42253 Référence CVE CVE-2026-42402 https://www.cve.org/CVERecord?id=CVE-2026-42402 Référence CVE CVE-2026-42403 https://www.cve.org/CVERecord?id=CVE-2026-42403 Référence CVE CVE-2026-42404 https://www.cve.org/CVERecord?id=CVE-2026-42404 Référence CVE CVE-2026-42561 https://www.cve.org/CVERecord?id=CVE-2026-42561 Référence CVE CVE-2026-42588 https://www.cve.org/CVERecord?id=CVE-2026-42588 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=CVE-2026-43450 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43869 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-42256 Référence CVE CVE-2026-42257 https://www.cve.org/CVERecord?id=CVE-2026-42257 Référence CVE CVE-2026-42258 https://www.cve.org/CVERecord?id=CVE-2026-42258 Référence CVE CVE-2026-42264 https://www.cve.org/CVERecord?id=CVE-2026-42264 Référence CVE CVE-2026-42338 https://www.cve.org/CVERecord?id=CVE-2026-42338 Référence CVE CVE-2026-42502 https://www.cve.org/CVERecord?id=CVE-2026-42502 Référence CVE CVE-2026-42506 https://www.cve.org/CVERecord?id=CVE-2026-42506 Référence CVE CVE-2026-42508 https://www.cve.org/CVERecord?id=CVE-2026-42508 Référence CVE CVE-2026-42578 https://www.cve.org/CVERecord?id=CVE-2026-42578 Référence CVE CVE-2026-42588 https://www.cve.org/CVERecord?id=CVE-2026-42588 Référence CVE CVE-2026-44024 https://www.cve.org/CVERecord?id=CVE-2026-44024 Référence CVE CVE-2026-44025 https://www.cve.org/CVERecord?id=CVE-2026-44025 Référence CVE CVE-2026-44160 https://www.cve.org/CVERecord?id=CVE-2026-44160 Référence CVE CVE-2026-44161 https://www.cve.org/CVERecord?id=CVE-2026-44161 Référence CVE CVE-2026-4424 https://www.cve.org/CVERecord?id=CVE-2026-4424 Référence CVE CVE-2026-44431 https://www.cve.org/CVERecord?id=CVE-2026-44431 Référence CVE CVE-2026-44486 https://www.cve.org/CVERecord?id=CVE-2026-44486 Référence CVE CVE-2026-44487 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-017842Apache Software FoundationのApache ActiveMQ等の複数製品における複数の脆弱性

Apache ActiveMQ Broker、Apache ActiveMQ All、およびApache ActiveMQにおける、不適切な入力検証およびコード生成の制御不備（コードインジェクションの脆弱性）について説明します。Apache ActiveMQ Classicは、Webコンソール上の/api/jolokia/でJolokia JMX-HTTPブリッジを公開しています。デフォルトのJolokiaアクセスポリシーでは、すべてのActiveMQ MBeans（org.apache.activemq:*）、特にBrokerService.addNetworkConnector(String)に対するexec操作を許可しています。認証された攻撃者は、VMトランスポートのbrokerConfigパラメータを「masterslave://」URLを用いてトリガーする細工されたディスカバリURIを使ってこれらの操作を呼び出すことが可能であり、ResourceXmlApplicationContextを使用してSpringのXMLアプリケーションコンテキストを読み込めます。SpringのResourceXmlApplicationContextは、BrokerServiceが構成を検証する前にすべてのシングルトンBeanをインスタンス化するため、Runtime.exec()のようなBeanファクトリメソッドを通じて、ブローカーのJVM上で任意のコードを実行します。この問題はApache ActiveMQ Brokerの5.19.7未満、6.0.0から6.2.6未満、Apache ActiveMQ Allの5.19.7未満、6.0.0から6.2.6未満、およびApache ActiveMQの5.19.7未満、6.0.0から6.2.6未満に影響します。ユーザーには、この問題を修正したバージョン5.19.7または6.2.6へアップグレードすることを推奨します。

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.
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 1 Jun 2026 · Last source change 2 Jun 2026, 03:55 UTC · CWE-20 · Improper Input Validation

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-33577
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
    < 5.19.7; 6.0.0 < 6.2.6 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 5.19.7; 6.0.0 < 6.2.6 · Fixed: Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update).
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-42588 to remediation: access.redhat.com/CVE-2026-42588.
    Before
    remediation: access.redhat.com/CVE-2026-42588
    After
    remediation: access.redhat.com/CVE-2026-42588
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    activemq-broker as a component of Red Hat AMQ Broker 7; activemq-all as a component of Red Hat Fuse 7; activemq-broker as a component of Red Hat Fuse 7
    After
    activemq-all as a component of Red Hat Fuse 7; activemq-broker as a component of Red Hat Fuse 7 · Fixed: Red Hat AMQ Broker 7.13.6; Red Hat AMQ Broker 7.14.1
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-33577↗Red Hat Product Security security advisory↗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-42588 · cve.blacktree.nl