CVE-2026-111822

validatedZero produced an exploit or a check.

GHSA-5jrv-f37p-8c36 ↗EUVD-2026-116827 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache ActiveMQ >= 6.0.0, < 6.3.3; < 5.19.12
fixed in 6.3.3, 5.19.12
ETK-2026-3484Zero's internal tracking ID, independent of the CVE number., permanent identifier
+40mTTV
31mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+40magent stopped
0
+10min
+20min
+30min

description

Apache ActiveMQ and ActiveMQ Runtime Config retain write access for some already-authenticated connections after that access has been revoked through runtime configuration. An attacker or user with a connection established before the permission change may continue sending messages to the affected destination; the issue requires runtime authorization changes and a pre-existing authenticated connection.

mitigation

Upgrade Apache ActiveMQ and ActiveMQ Runtime Config to 6.3.3 or 5.19.12 or later. Until upgraded, restrict or terminate existing client connections after revoking destination write permissions.

fixed in 6.3.3, 5.19.12

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 10:12Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-04 10:12Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-111822

{
  "etk_id": "ETK-2026-3484",
  "cve_id": "CVE-2026-111822",
  "display_id": "CVE-2026-111822",
  "ghsa_id": "GHSA-5jrv-f37p-8c36",
  "euvd_id": "EUVD-2026-116827",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stale write authorization caching in Apache ActiveMQ",
  "summary": "Apache ActiveMQ and ActiveMQ Runtime Config retain write access for some already-authenticated connections after that access has been revoked through runtime configuration. An attacker or user with a connection established before the permission change may continue sending messages to the affected destination; the issue requires runtime authorization changes and a pre-existing authenticated connection.",
  "mitigation": "Upgrade Apache ActiveMQ and ActiveMQ Runtime Config to 6.3.3 or 5.19.12 or later. Until upgraded, restrict or terminate existing client connections after revoking destination write permissions.",
  "vendor": "Apache Software Foundation",
  "product": "Apache ActiveMQ",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.0.0, < 6.3.3",
        ">= 0, < 5.19.12"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.3.3",
        "5.19.12"
      ],
      "package_name": "org.apache.activemq:apache-activemq",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.0.0, < 6.3.3",
        ">= 0, < 5.19.12"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.3.3",
        "5.19.12"
      ],
      "package_name": "org.apache.activemq:activemq-runtime-config",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 30.52626495,
  "t0_at": "2026-11-04T10:12:08.183000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T10:51:52.046574+00:00",
      "days": 0.027591013587962964,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T10:12:08.183000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-04T10:12:08.183000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T10:12:08.183000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111822"
    }
  }
}

published 2026-11-04 10:21Z
last change 2026-11-04 14:42Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.