{
  "@id": "urn:uuid:1097b284-5bc5-4884-baaa-c46486297489",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-11-09T17:39:53.597807+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.37.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.37.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:39:53.597807+00:00",
      "status_notes": "Vulnerability CVE-2021-26118 does not affect version 2.37.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol. CVE-2021-26118 is not present in target Apache ActiveMQ Artemis 2.37.0. The vulnerability allowed advisory messages in the OpenWire protocol to bypass access control policies by routing them through a special \"advisory session\" that had security disabled. The fix (commit e5566d5211, ARTEMIS-2964) was already present in upstream Apache ActiveMQ Artemis 2.37.0 before TuxCare onboarded it. The vulnerable code patterns (advisorySession field, setAdvisorySession/getAdvisorySession methods, addSession with internal parameter calling disableSecurity) are completely absent from the target. Advisory messages now route directly through server.getPostOffice().route(), which respects normal access control policies.\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 target Apache ActiveMQ Artemis 2.37.0. The vulnerability allowed advisory messages in the OpenWire protocol to bypass access control policies by routing them through a special \"advisory session\" that had security disabled. The fix (commit e5566d5211, ARTEMIS-2964) was already present in upstream Apache ActiveMQ Artemis 2.37.0 before TuxCare onboarded it. The vulnerable code patterns (advisorySession field, setAdvisorySession/getAdvisorySession methods, addSession with internal parameter calling disableSecurity) are completely absent from the target. Advisory messages now route directly through server.getPostOffice().route(), which respects normal access control policies.\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.37.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.37.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:39:53.597807+00:00",
      "status_notes": "Vulnerability CVE-2026-32642 affects version 2.37.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol.",
      "vulnerability": {
        "name": "CVE-2026-32642"
      },
      "action_statement": "Vulnerability CVE-2026-32642 affects version 2.37.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol."
    },
    {
      "status": "fixed",
      "products": [
        {
          "@id": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.37.0-tuxcare.4",
          "identifiers": {
            "purl": "pkg:maven/org.apache.activemq/artemis-openwire-protocol@2.37.0-tuxcare.4"
          }
        }
      ],
      "timestamp": "2026-11-09T17:39:53.597807+00:00",
      "status_notes": "Vulnerability CVE-2026-67593 is fixed in version 2.37.0-tuxcare.4 of org.apache.activemq:artemis-openwire-protocol.",
      "vulnerability": {
        "name": "CVE-2026-67593"
      }
    }
  ]
}