CVE-2026-57568

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th 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-2026-102187 (ENISA EUVD)Source: ENISA EUVD

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

A fix is available — apply it.

Lychee is a free, open-source photo-management tool. Prior to 7.6.0, Lychee permits an authenticated user with album-edit permissions to store a javascript URI in an album or photo Markdown description because config/markdown.php enables allow_unsafe_links. app/Http/Resources/Models/Utils/PreformattedPhotoData.php and app/Http/Resources/Models/Utils/PreFormattedAlbumData.php convert the description to HTML, and the gallery components PhotoDetails.vue, Overlay.vue, PhotoThumb.vue, AlbumHero.vue, and AlbumCard.vue render that HTML with v-html. A visitor, including an unauthenticated visitor to a public album, who clicks the rendered link executes attacker-controlled JavaScript in the Lychee origin, which can expose session data or enable authenticated requests in the victim's context. This gallery-view flaw is distinct from CVE-2026-33738, which addressed feed rendering. This issue is fixed in version 7.6.0.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
20th
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.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 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.

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 15, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

v7.6.0

Patch available: LycheeOrg/Lychee v7.6.0

https://github.com/LycheeOrg/Lychee/releases/tag/v7.6.0
GitHub commit Patch Available

commit f0604ead5889 (LycheeOrg/Lychee)

Patch available: LycheeOrg/Lychee v7.6.0 (contains commit f0604ead5889)

https://github.com/LycheeOrg/Lychee/commit/f0604ead5889bfed404d6f5e1a9205f945172c7e
GitHub pull request Patch Available

Update Markdown configuration to a more secure practice

Patch available: LycheeOrg/Lychee v7.6.0 (PR #4377 merged 2026-05-26)

https://github.com/LycheeOrg/Lychee/pull/4377
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored XSS via Markdown javascript: Links in Photo and Album Descriptions (Gallery View) · Advisory · LycheeOrg/Lychee · GitHub

https://github.com/LycheeOrg/Lychee/security/advisories/GHSA-pgfr-x389-5p2h

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 24× 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-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-29 16:37 UTCEG score recompute
  3. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-25 14:17 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-22 21:06 UTCEG score recompute
  12. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-18 03:28 UTCEG score recompute
  18. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-16 18:35 UTCEG score recompute
  20. 2026-10-16 18:06 UTCEG score recompute
  21. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-10-15 17:30 UTCEG score recompute
  23. 2026-10-15 16:39 UTCEG score recomputeFirst assessed: 5.7 MEDIUM
  24. 2026-10-15 16:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57568?
CVE-2026-57568 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. Lychee is a free, open-source photo-management tool. Prior to 7.6.0, Lychee permits an authenticated user with album-edit permissions to store a javascript URI in an album or photo Markdown description because config/markdown.php enables allowunsafelinks.…
When was the CVE record for CVE-2026-57568 published?
The CVE record for CVE-2026-57568 was published on October 15, 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-57568 actively exploited?
CVE-2026-57568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57568?
CVE-2026-57568 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57568?
A fix for CVE-2026-57568 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-2026-57568

Explore →

Is Your Infrastructure Affected by CVE-2026-57568?

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