Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

RabbitMQ: Stored XSS via TLS peer-certificate DN in management UI

No KEV listing collectedCVSS not publishedFix not stated

Assessment

Severity
Important
CVSS base score
Not published
Impact
Not stated
Exploitation detected
Unknown: not stated by MSRC
Exploitability
Not assessed
Publicly disclosed
Unknown: not stated by MSRC
EPSS · 30-day forecast
No EPSS score collected
Customer action
Required: follow the MSRC remediation guidance
More details
Public detection template
No Nuclei template is listed in the current collected catalog
Component
Mariner
Weakness
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Issued by
GitHub_M
Published
3 Oct 2026 · September 2026
Last revised
16 Nov 2026Information published.

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software
3 affected products
  • azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0
  • azl3 rabbitmq-server 3.13.7-11 on Azure Linux 3.0
  • azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0

What changed

  1. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  2. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  3. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  4. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  5. Affected products: azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0 → azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-11 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0
  6. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  7. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  8. Affected products: azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0 → azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0
  9. Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
  10. Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  11. Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (48)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 17 Nov 2026 · 09:10:20 UTC Last revised5 Nov 2026 14:51 UTC → 16 Nov 2026 22:57 UTC
  2. 13 Nov 2026 · 12:10:20 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  3. 13 Nov 2026 · 12:10:20 UTC Source coverage: public-exploit-codeIncomplete → Current
  4. 13 Nov 2026 · 12:10:20 UTC Source coverage: first-epssIncomplete → Current
  5. 13 Nov 2026 · 12:10:20 UTC Source coverage: msrc-cvrfIncomplete → Current
  6. 13 Nov 2026 · 11:07:20 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  7. 13 Nov 2026 · 11:07:20 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  8. 13 Nov 2026 · 11:07:20 UTC Source coverage: first-epssCurrent → Incomplete
  9. 13 Nov 2026 · 11:07:20 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  10. 6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  11. 6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
  12. 6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
  13. 6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
  14. 6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  15. 6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  16. 6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
  17. 6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  18. 6 Nov 2026 · 09:07:49 UTC Last revised1 Nov 2026 14:54 UTC → 5 Nov 2026 14:51 UTC
  19. 6 Nov 2026 · 09:07:49 UTC Affected productsazl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0 → azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-11 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0
  20. 2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  21. 2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
  22. 2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
  23. 2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
  24. 2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  25. 2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  26. 2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
  27. 2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  28. 2 Nov 2026 · 09:04:36 UTC Last revised3 Oct 2026 01:52 UTC → 1 Nov 2026 14:54 UTC
  29. 2 Nov 2026 · 09:04:36 UTC Affected productsazl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0 → azl3 rabbitmq-server 3.13.7-10 on Azure Linux 3.0, azl3 rabbitmq-server 3.13.7-9 on Azure Linux 3.0
  30. 29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
  31. 29 Oct 2026 · 20:19:26 UTC EPSSNot scored → No EPSS score collected
  32. 29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
  33. 29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → Unknown: not stated by MSRC
  34. 29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → Unknown: not stated by MSRC
  35. 23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
  36. 23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  37. 23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
  38. 23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
  39. 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
  40. 23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
  41. 23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
  42. 23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
  43. 23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  44. 23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
  45. 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
  46. 23 Oct 2026 · 08:31:50 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  47. 18 Oct 2026 · 14:54:30 UTC Link: September 2026/security?release=2026-Sep#cves
  48. 14 Oct 2026 · 11:22:42 UTC Source coverage: msrc-cvrfIncomplete → Current

Explore global source statements, affected packages and advisory history for CVE-2026-66077. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-66077

Published

RabbitMQ: Stored XSS via TLS peer-certificate DN in management UI

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, The management UI uses EJS 1.0 in which <%= ... %> does NOT HTML-escape. connection.ejs:135 renders <%= connection.ssl_details.peer_cert_subject %> (and peer_cert_issuer) directly into the page. The same pattern appears in streamConnection.ejs:102,106,110. The values come from rabbit_ssl:peer_cert_subject/1 which formats the DN as a string without HTML escaping. The verifier corrected the original researcher's claim: this is reachable only when the listener is configured with verify_peer (so the certificate must be signed by a CA in the broker's trust store, not arbitrary self-signed); however, in deployments using mTLS for client authentication, any user who can request a certificate from the organisational CA controls the Subject CN. An attacker who can obtain a TLS client certificate signed by a CA the broker trusts (with verify_peer enabled) can embed JavaScript in the certificate's Subject DN. When any administrator views that connection in the management UI, the script executes in the admin's browser session, allowing full account takeover (create users, export definitions, etc.). The management UI's CSP includes 'unsafe-inline', so inline script execution is not blocked. Preconditions include TLS listener configured with ssl_options.verify = verify_peer Attacker can obtain a CA-signed client certificate with attacker-chosen Subject (e.g. self-service corporate PKI, or rabbitmq_trust_store plugin in use) Administrator views the connection detail page. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Source published
23 Sep 2026 20:03:42 UTC
Source modified
29 Sep 2026 02:14:16 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 7.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 10:11 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current