CVE-2026-82266

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-28. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-67797 (ENISA EUVD) · GHSA-qp5m-mrqw-6pxr (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists redpanda-data redpanda versions up to and including 26.2.2 as affected. No release containing a fix is confirmed on record.

Redpanda through 26.2.2 binds the Admin API to 0.0.0.0:9644 with admin_api_require_auth defaulting to false, treating unauthenticated requests as superusers. Attackers can reach port 9644 without credentials to create and delete broker accounts, modify cluster configuration, and disrupt partition replication.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Oct 16, 2026
No fix on record yet. Sources: github.
Web page

Redpanda Admin API Unauthenticated Superuser Access via Default Configuration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/redpanda-admin-api-unauthenticated-superuser-access-via-default-configuration
Web page

Unauthenticated Admin API Access in Default Configuration · Issue #30989 · redpanda-data/redpanda · GitHub

https://github.com/redpanda-data/redpanda/issues/30989
GitHub advisory

redpanda/src/v/security/request_auth.cc at 3cfce474a872090e7c74d14181885f5838c54cf2 · redpanda-data/redpanda · GitHub

https://github.com/redpanda-data/redpanda/blob/3cfce474a872090e7c74d14181885f5838c54cf2/src/v/security/request_auth.cc
Web page

redpanda/conf/redpanda.yaml at 3cfce474a872090e7c74d14181885f5838c54cf2 · redpanda-data/redpanda · GitHub

https://github.com/redpanda-data/redpanda/blob/3cfce474a872090e7c74d14181885f5838c54cf2/conf/redpanda.yaml
Web page

GitHub - redpanda-data/redpanda: Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM! · GitHub

https://github.com/redpanda-data/redpanda

Vendor Advisories for CVE-2026-82266(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 138× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 375 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 275 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-10-26 15:00 UTCEG score recompute
  3. 2026-10-26 15:00 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-25 16:04 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-25 13:58 UTCEG score recompute
  7. 2026-10-24 17:59 UTCEG score recompute
  8. 2026-10-24 17:59 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-23 19:58 UTCEG score recompute
  11. 2026-10-23 19:58 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  13. 2026-10-22 21:47 UTCEG score recompute
  14. 2026-10-22 21:47 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  16. 2026-10-21 23:46 UTCEG score recompute
  17. 2026-10-21 23:46 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  19. 2026-10-21 01:45 UTCEG score recompute
  20. 2026-10-21 01:45 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  22. 2026-10-20 03:44 UTCEG score recompute
  23. 2026-10-20 03:44 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-19 04:23 UTCEG score recompute
Show 75 more
  1. 2026-10-19 04:22 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-18 06:18 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-18 03:08 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-17 06:02 UTCEG score recompute
  6. 2026-10-17 06:02 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-16 07:08 UTCEG score recompute
  9. 2026-10-16 07:08 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-15 05:57 UTCEG score recompute
  12. 2026-10-15 05:57 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-14 01:34 UTCEG score recompute
  15. 2026-10-14 01:34 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-12 21:45 UTCEG score recompute
  18. 2026-10-12 21:45 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-12 14:55 UTCEG score recompute
  21. 2026-10-12 05:19 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-11 19:20 UTCEG score recompute
  23. 2026-10-11 16:36 UTCEG score recompute
  24. 2026-10-11 13:54 UTCEG score recompute
  25. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  26. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  27. 2026-10-10 13:38 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-10 09:39 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-10 05:17 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-10 00:54 UTCEG score recompute
  31. 2026-10-10 00:53 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  33. 2026-10-09 06:52 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-09 02:41 UTCEG score recompute
  35. 2026-10-09 02:40 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  37. 2026-10-08 08:46 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-08 04:49 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-08 00:52 UTCEG score recompute
  40. 2026-10-08 00:52 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  42. 2026-10-07 08:59 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-07 05:02 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-07 01:05 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-06 20:28 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-06 15:55 UTCEG score recompute
  47. 2026-10-06 15:55 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  49. 2026-10-06 11:24 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-06 07:28 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-06 00:48 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-05 20:46 UTCEG score recompute
  53. 2026-10-05 20:46 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  55. 2026-10-05 16:49 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-10-05 11:34 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-05 07:37 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-05 03:40 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-04 23:33 UTCEG score recompute
  60. 2026-10-04 23:33 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  62. 2026-10-04 19:36 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-10-04 13:51 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-04 09:55 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-04 05:51 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-10-04 01:54 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-03 21:35 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-10-03 17:38 UTCEG score recompute
  69. 2026-10-03 17:38 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  71. 2026-10-03 13:41 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-03 06:48 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-10-03 02:51 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-02 22:54 UTCGHSA enrichmentGHSA-qp5m-mrqw-6pxr · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-10-02 18:50 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-82266?
CVE-2026-82266 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. Redpanda through 26.2.2 binds the Admin API to 0.0.0.0:9644 with adminapirequire_auth defaulting to false, treating unauthenticated requests as superusers. Attackers can reach port 9644 without credentials to create and delete broker accounts, modify cluster configuration, and disrupt partition…
When was CVE-2026-82266 made public?
CVE-2026-82266 was made public on July 1, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-82266 actively exploited?
CVE-2026-82266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82266?
CVE-2026-82266 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82266?
No fix for CVE-2026-82266 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists redpanda-data redpanda versions up to and including 26.2.2 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-82266 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82266

Explore →

Is Your Infrastructure Affected by CVE-2026-82266?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.