CVE-2026-1221

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-01-20. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-3461 (ENISA EUVD) · GHSA-wm49-2vmh-chv3 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate 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.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Update firmware to version v1.03.23.01 or later (from the CVE record's solution, TWCERT/CC) — apply it.

PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has a Use of Hard-coded Credentials vulnerability, allowing unauthenticated remote attackers to log in to the database using hardcoded database credentials stored in the firmware.

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.5% × 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: Update firmware to version v1.03.23.01 or later (from the CVE record's solution, TWCERT/CC). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, and whom BOD 26-04 binds: 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).

Update firmware to version v1.03.23.01 or later (from the CVE record's solution, TWCERT/CC). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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

January 20, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Nov 1, 2026
Fix named in the CVE record's solution (TWCERT/CC). Sources: cert.
CERT

普羅通信|PrismX MX100 AP controller - 存在3個漏洞-TWCERT/CC台灣電腦網路危機處理暨協調中心|企業資安通報協處|資安情資分享|漏洞通報|資安聯盟|資安電子報

https://www.twcert.org.tw/tw/cp-132-10642-3b808-1.html
CERT

BROWAN COMMUNICATIONS |PrismX MX100 AP controller - 3 Vulnerabilitires-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-10643-2f8d7-2.html

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 58× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 276 rows 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 176 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-1221?
CVE-2026-1221 is a critical-severity vulnerability; its CVE record was published on January 20, 2026. PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has a Use of Hard-coded Credentials vulnerability, allowing unauthenticated remote attackers to log in to the database using hardcoded database credentials stored in the firmware.
When was CVE-2026-1221 made public?
CVE-2026-1221 was made public on January 20, 2026: that is the date its CVE record's CNA, TWCERT/CC, gives for when the vulnerability was made public. The CVE record itself was published on January 20, 2026. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-1221 actively exploited?
CVE-2026-1221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1221?
CVE-2026-1221 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-1221?
The CVE record's solution for CVE-2026-1221, written by its CNA TWCERT/CC, names the fix: "Update firmware to version v1.03.23.01 or later."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-1221?

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