CVE-2026-27128

MEDIUMNVD 4.84.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-7401 (ENISA EUVD) · GHSA-6fx5-5cw5-4897 (GitHub Security Advisories)Source: ENISA EUVD

4.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, a Time-of-Check-Time-of-Use (TOCTOU) race condition exists in Craft CMS’s token validation service for tokens that explicitly set a limited usage. The getTokenRoute() method reads a token’s usage count, checks if it’s within limits, then updates the database in separate non-atomic operations. By sending concurrent requests, an attacker can use a single-use impersonation token multiple times before the database update completes. To make this work, an attacker needs to obtain a valid user account impersonation URL with a non-expired token via some other means and exploit a race condition while bypassing any rate-limiting rules in place. For this to be a privilege escalation, the impersonation URL must include a token for a user account with more permissions than the current user. Versions 4.16.19 and 5.8.23 patch the issue.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/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)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
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 (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

February 24, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Race condition in Token Service potentially allows for token usage greater than the token limit · Advisory · craftcms/cms · GitHub

https://github.com/craftcms/cms/security/advisories/GHSA-6fx5-5cw5-4897
GitHub commit Patch Available

commit 3e4afe182799 (craftcms/cms)

Patch available: craftcms/cms 6.0.0-alpha.3 (contains commit 3e4afe182799)

https://github.com/craftcms/cms/commit/3e4afe18279951c024c64896aa2b93cda6d95fdf

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composercraftcms/cms @ 4.16.19 (fixes >= 4.5.0-RC1, <= 4.16.18)—ghsa
composercraftcms/cms @ 5.8.23 (fixes >= 5.0.0-RC1, <= 5.8.22)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
craftcms/cms5.0.0 ... 5.8.9 (144 versions)
  • 4.5.0-RC1 up to 4.16.19: fixed in 4.16.19
  • 5.0.0-RC1 up to 5.8.23: fixed in 5.8.23
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 97 of 101 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-27128?
CVE-2026-27128 is a medium-severity vulnerability; its CVE record was published on February 24, 2026. Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, a Time-of-Check-Time-of-Use (TOCTOU) race condition exists in Craft CMS’s token validation service for tokens that explicitly set a limited usage. The getTokenRoute() method reads a…
When was the CVE record for CVE-2026-27128 published?
The CVE record for CVE-2026-27128 was published on February 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-27128 actively exploited?
CVE-2026-27128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27128?
CVE-2026-27128 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-27128?
A fix for CVE-2026-27128 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27128

Explore →

Is Your Infrastructure Affected by CVE-2026-27128?

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

Book a Demo →Browse All CVEs