CVE-2025-24900

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th 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

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

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

A fix is available — apply it.

Concorde, formerly know as Nexkey, is a fork of the federated microblogging platform Misskey. Due to a lack of CSRF countermeasures and improper settings of cookies for MediaProxy authentication, there is a vulnerability that allows MediaProxy authentication to be bypassed. In versions prior to 12.25Q1.1, the authentication cookie does not have the SameSite attribute. This allows an attacker to bypass MediaProxy authentication and load any image without restrictions under certain circumstances. In versions prior to 12.24Q2.3, this cookie was also used to authenticate the job queue management page (bull-board), so bull-board authentication is also bypassed. This may enable attacks that have a significant impact on availability and integrity. The affected versions are too old to be covered by this advisory, but the maintainers of Concorde strongly recommend not using older versions. Version 12.25Q1.1 contains a patch. There is no effective workaround other than updating.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
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 (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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, 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).

A fix is available. 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 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.

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

February 11, 2025

Last Modified

April 15, 2026

Advisory Details (3)

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

CSRF vulnerability due to insecure configuration of authentication cookie attributes · Advisory · nexryai/concorde · GitHub

https://github.com/nexryai/concorde/security/advisories/GHSA-5hgq-9vw8-7v87
GitHub commit Patch Available

commit f3f54bde6a37 (nexryai/concorde)

Patch available: nexryai/concorde v12.25Q1.1 (contains commit f3f54bde6a37)

https://github.com/nexryai/concorde/commit/f3f54bde6a37ad310f83ae46de54a286c4b74059
GitHub commit Patch Available

commit 2309b4a29282 (nexryai/concorde)

Patch available: nexryai/concorde v12.25Q1.1 (contains commit 2309b4a29282)

https://github.com/nexryai/concorde/commit/2309b4a292828ddba4d57cf0e914bc433095871d

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 226 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 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-24900?
CVE-2025-24900 is a high-severity vulnerability; its CVE record was published on February 11, 2025. Concorde, formerly know as Nexkey, is a fork of the federated microblogging platform Misskey. Due to a lack of CSRF countermeasures and improper settings of cookies for MediaProxy authentication, there is a vulnerability that allows MediaProxy authentication to be bypassed. In versions prior to…
When was the CVE record for CVE-2025-24900 published?
The CVE record for CVE-2025-24900 was published on February 11, 2025. 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-24900 actively exploited?
CVE-2025-24900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-24900?
CVE-2025-24900 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2025-24900?
A fix for CVE-2025-24900 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-24900?

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