CVE-2026-67410

validatedZero produced an exploit or a check.

GHSA-f9f2-q3jf-wfj3 ↗EUVD-2026-87238 ↗

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).−65dkevAttacks confirmed in the real world.
broadcom rabbitmq:rabbitmq-server >= 4.3.0, < 4.3.3; >= 4.2.0, < 4.2.9; >= 4.1.0, < 4.1.14
fixed in 4.3.3, 4.2.9, 4.1.14
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-5139Zero's internal tracking ID, independent of the CVE number., permanent identifier
+57dTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
public poc−2.1motrigger signal (cve.org) +0mocheck available+1.9moagent stopped
−1mo
0
+1mo

description

RabbitMQ Server deployments with the Management UI enabled, OAuth2 enabled, and a configured management OAuth2 client secret are affected. An unauthenticated party able to reach the Management UI port can obtain the client secret, which may permit impersonation of the UI client to the identity provider or access to resources granted to that client.

mitigation

Upgrade RabbitMQ Server to 4.3.3, 4.2.9, or 4.1.14, as appropriate for your release line. Until upgraded, avoid OAuth2 flows requiring a client secret, or disable the Management UI or OAuth2 authentication backend.

fixed in 4.3.3, 4.2.9, 4.1.14

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.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.41%36th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-25 16:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−65d
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-09-25 16:32Z
  2. 2026-09-25 16:32Z
  3. 2026-09-25 16:32Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-5139",
  "cve_id": "CVE-2026-67410",
  "display_id": "CVE-2026-67410",
  "ghsa_id": "GHSA-f9f2-q3jf-wfj3",
  "euvd_id": "EUVD-2026-87238",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OAuth2 client-secret exposure in RabbitMQ Management UI",
  "summary": "RabbitMQ Server deployments with the Management UI enabled, OAuth2 enabled, and a configured management OAuth2 client secret are affected. An unauthenticated party able to reach the Management UI port can obtain the client secret, which may permit impersonation of the UI client to the identity provider or access to resources granted to that client.",
  "mitigation": "Upgrade RabbitMQ Server to 4.3.3, 4.2.9, or 4.1.14, as appropriate for your release line. Until upgraded, avoid OAuth2 flows requiring a client secret, or disable the Management UI or OAuth2 authentication backend.",
  "vendor": "broadcom",
  "product": "rabbitmq:rabbitmq-server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.3.0, < 4.3.3"
      ],
      "ecosystem": "rabbitmq",
      "fixed_versions": [
        "4.3.3"
      ],
      "package_name": "rabbitmq-server",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.2.0, < 4.2.9"
      ],
      "ecosystem": "rabbitmq",
      "fixed_versions": [
        "4.2.9"
      ],
      "package_name": "rabbitmq-server",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.1.0, < 4.1.14"
      ],
      "ecosystem": "rabbitmq",
      "fixed_versions": [
        "4.1.14"
      ],
      "package_name": "rabbitmq-server",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0041,
  "epss_percentile": 0.36,
  "epss_asof": "2026-11-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 7.540907483333333,
  "t0_at": "2026-09-25T16:32:51.225000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-21T13:33:20.979680+00:00",
      "days": 56.875344382870374,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T16:32:51.225000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-07-23T01:04:03+00:00",
      "days": -64.64500260416666,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T16:32:51.225000+00:00",
      "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3"
    },
    "trigger_signal": {
      "at": "2026-09-25T16:32:51.225000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-25T16:32:51.225000+00:00",
      "url": "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-f9f2-q3jf-wfj3"
    }
  }
}

published 2026-11-21 13:25Z
last change 2026-11-21 14:47Z

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.