CVE-2025-8853

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 2025-08-11. 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-2025-24134 (ENISA EUVD) · GHSA-xghr-g5w9-xwr9 (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.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

Official Document Management System developed by 2100 Technology has an Authentication Bypass vulnerability, allowing unauthenticated remote attackers to obtain any user's connection token and use it to log into the system as that user.

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.8% × 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 to version 5.0.90 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.8%
EPSS %ILE
55th
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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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 to version 5.0.90 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

August 11, 2025

Last Modified

June 17, 2026

Advisory Details (4)

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

二一零零科技|公文管理系統 - Authentication Bypass-TWCERT/CC台灣電腦網路危機處理暨協調中心|企業資安通報協處|資安情資分享|漏洞通報|資安聯盟|資安電子報

https://www.twcert.org.tw/tw/cp-132-10319-adc18-1.html
CERT

2100 Technology|Official Document Management System - Authentication Bypass-TWCERT/CC Taiwan Computer Emergency Response Team/Coordination Center

https://www.twcert.org.tw/en/cp-139-10320-ad540-2.html
Web page

CHT Security Red Team Discovered a Vulnerability in a Well-Known Official Document Management System.|中華資安國際 CHT Security Co., Ltd.

https://www.chtsecurity.com/news/a9a90f0b-c2cb-4c66-b3d1-bc7f252fd108
Web page

中華資安國際發現CVE弱點,國內某公文系統存在驗證機制失效弱點,可能導致敏感資料洩漏|中華資安國際 CHT Security Co., Ltd.

https://www.chtsecurity.com/news/8618a2f0-390a-4506-9ff8-a9e74030d19e

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-8853?
CVE-2025-8853 is a critical-severity vulnerability; its CVE record was published on August 11, 2025. Official Document Management System developed by 2100 Technology has an Authentication Bypass vulnerability, allowing unauthenticated remote attackers to obtain any user's connection token and use it to log into the system as that user.
When was CVE-2025-8853 made public?
CVE-2025-8853 was made public on August 11, 2025: 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 August 11, 2025. 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-2025-8853 actively exploited?
CVE-2025-8853 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8853?
CVE-2025-8853 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-2025-8853?
The CVE record's solution for CVE-2025-8853, written by its CNA TWCERT/CC, names the fix: "Update to version 5.0.90 or later".

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-8853?

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