{
  "@id": "urn:uuid:a25d8689-c3f4-4fa6-9400-96fc576a2f89",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 2,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-09T17:13:00.039712+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:12:02.186715+00:00",
      "status_notes": "Vulnerability CVE-2021-26118 does not affect version 2.40.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol. CVE-2021-26118 is not present in ActiveMQ Artemis 2.40.0. The vulnerability involved advisory messages being sent through a security-disabled session (session ID -1), bypassing access control checks. The upstream fix (ARTEMIS-2964, commit e5566d5211) was already included in version 2.40.0 before TuxCare onboarded this release. Advisory messages now route directly through server.getPostOffice().route() with proper access control enforcement, rather than through a special session with disableSecurity() called. Code inspection confirms: (1) fireAdvisory() routes via post office, (2) advisorySession field and methods removed from OpenWireConnection, (3) no session ID -1 creation logic, (4) no disableSecurity() calls for advisory purposes.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.16.0), NVD (= 2.15.0), cve.org (< 2.16.0), Snyk (< 2.16.0).",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2021-26118"
      },
      "impact_statement": "CVE-2021-26118 is not present in ActiveMQ Artemis 2.40.0. The vulnerability involved advisory messages being sent through a security-disabled session (session ID -1), bypassing access control checks. The upstream fix (ARTEMIS-2964, commit e5566d5211) was already included in version 2.40.0 before TuxCare onboarded this release. Advisory messages now route directly through server.getPostOffice().route() with proper access control enforcement, rather than through a special session with disableSecurity() called. Code inspection confirms: (1) fireAdvisory() routes via post office, (2) advisorySession field and methods removed from OpenWireConnection, (3) no session ID -1 creation logic, (4) no disableSecurity() calls for advisory purposes.\n\nAdvisory cross-check (dlmn): outside the affected ranges of GitHub (< 2.16.0), NVD (= 2.15.0), cve.org (< 2.16.0), Snyk (< 2.16.0)."
    },
    {
      "status": "affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:12:02.186715+00:00",
      "status_notes": "Vulnerability CVE-2026-32642 affects version 2.40.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol.",
      "vulnerability": {
        "name": "CVE-2026-32642"
      },
      "action_statement": "Vulnerability CVE-2026-32642 affects version 2.40.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.40.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:13:00.039712+00:00",
      "status_notes": "Vulnerability CVE-2026-67593 is fixed in version 2.40.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol.",
      "vulnerability": {
        "name": "CVE-2026-67593"
      }
    }
  ]
}