CVE-2026-103974

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th 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
Elevated

Also known asEUVD-2026-101591 (ENISA EUVD)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

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

lichess.org is the forever free, adless and open source chess server. Prior to commit c54596c9e1569d378fe20f80d4c790c6fdee54c4, a user who can add a chapter to a study can place attacker-controlled text in the PGN Annotator tag, which becomes Comment.Author.External and is returned verbatim by authorText. When a study node has at least two comments, ui/analyse/src/treeView/inlineView.ts interpolates that author string into HTML passed to the innerHTML hook without escaping it. Opening the affected study can therefore render stored attacker-controlled HTML and CSS for other viewers, including navigation to an attacker-controlled site, content spoofing, and CSS-based data exposure, although the site's content security policy blocks injected JavaScript. This vulnerability is fixed by commit c54596c9e1569d378fe20f80d4c790c6fdee54c4.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
40
EG Risk 40/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
0.2%
EPSS %ILE
11th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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; Track* at high (mission-essential systems).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

Exploitation public PoC (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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

October 14, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. No fix on record yet. Sources: github_commit, github.
GitHub commit

commit c54596c9e156 (lichess-org/lila)

Fix landed in lichess-org/lila commit c54596c9e156 — awaiting tagged release

https://github.com/lichess-org/lila/commit/c54596c9e1569d378fe20f80d4c790c6fdee54c4
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored HTML Injection via PGN Annotator Tag in Studies · Advisory · lichess-org/lila · GitHub

https://github.com/lichess-org/lila/security/advisories/GHSA-43g7-r6hp-ccf8

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-28 02:55 UTCOSV refresh
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-18 05:09 UTCEG score recompute
  20. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-16 20:13 UTCEG score recompute
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-14 20:27 UTCEG score recompute
  25. 2026-10-14 19:45 UTCEG score recompute
Show 3 more
  1. 2026-10-14 19:37 UTCEG score recompute
  2. 2026-10-14 18:37 UTCEG score recomputeFirst assessed: 5.4 MEDIUM
  3. 2026-10-14 18:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103974?
CVE-2026-103974 is a medium-severity vulnerability; its CVE record was published on October 14, 2026. lichess.org is the forever free, adless and open source chess server. Prior to commit c54596c9e1569d378fe20f80d4c790c6fdee54c4, a user who can add a chapter to a study can place attacker-controlled text in the PGN Annotator tag, which becomes Comment.Author.External and is returned verbatim by…
When was the CVE record for CVE-2026-103974 published?
The CVE record for CVE-2026-103974 was published on October 14, 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 October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-103974 actively exploited?
CVE-2026-103974 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103974?
CVE-2026-103974 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103974?
No fix for CVE-2026-103974 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-2026-103974

Explore →

Is Your Infrastructure Affected by CVE-2026-103974?

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

Book a Demo →Browse All CVEs