CVE-2025-27621

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2025-210733 (ENISA EUVD)Source: ENISA EUVD

7.7EG
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.5%CVSS: 7.7Exploit: None knownExposed services: Not assessed

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

UpTrain is an open-source platform to evaluate and improve generative AI applications. In version 0.7.1 and prior, the UpTrain backend creates a new default user with a static username, where the username is also used as the default API key. The UpTrain backend also has an open CORS policy. Using these two primitives, any website can make a authenticated cross-origin request to the UpTrain instance by providing the default API key in the header uptrain-access-token. This issue may allow arbitrary websites to perform privileged operations on the UpTrain instance, as if they were the default logged in user. As of time of publication, no known patches are available.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 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 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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
39th
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 (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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: 14 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 within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 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 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

August 17, 2026

Last Modified

September 29, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
No fix on record yet. Sources: github.
GitHub advisory

GHSL-2024-198_GHSL-2024-199: Zero click RCE in Uptrain - CVE-2025-27621, CVE-2025-27770 | GitHub Security Lab

https://securitylab.github.com/advisories/GHSL-2024-198_GHSL-2024-199_Uptrain/
Web page

uptrain/uptrain/dashboard/backend/app.py at a31cc14eddcb6c0b0b12cbed15f086d98c441c6f · uptrain-ai/uptrain · GitHub

https://github.com/uptrain-ai/uptrain/blob/a31cc14eddcb6c0b0b12cbed15f086d98c441c6f/uptrain/dashboard/backend/app.py#L105

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-27621?
CVE-2025-27621 is a high-severity vulnerability; its CVE record was published on August 17, 2026. UpTrain is an open-source platform to evaluate and improve generative AI applications. In version 0.7.1 and prior, the UpTrain backend creates a new default user with a static username, where the username is also used as the default API key. The UpTrain backend also has an open CORS policy. Using…
When was the CVE record for CVE-2025-27621 published?
The CVE record for CVE-2025-27621 was published on August 17, 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 September 29, 2026; the record at its source may have been updated since.
Is CVE-2025-27621 actively exploited?
CVE-2025-27621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-27621?
CVE-2025-27621 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-27621?
No fix for CVE-2025-27621 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-27621

Explore →

Is Your Infrastructure Affected by CVE-2025-27621?

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