CVE-2026-57568 LycheeOrg CVE debrief

Who should care

Defenders responsible for Lychee installations, particularly those with public albums or unauthenticated access, should assess exposure and apply the patch to prevent potential JavaScript execution in the Lychee origin.

Why it matters

The stored XSS vulnerability in Lychee allows for JavaScript execution in the Lychee origin, potentially leading to exposure of session data or enabled authenticated requests in the victim's context. Defenders should prioritize verifying exposure and applying the patch.

• Potential exposure of session data
• Possible enabled authenticated requests in the victim's context
• Required verification of Lychee version and exposure
• Necessity for defenders to apply the patch

Technical summary

The vulnerability exists due to the allow_unsafe_links configuration in config/markdown.php, which permits an authenticated user to store a javascript URI in an album or photo Markdown description. The descriptions are converted to HTML and rendered with v-html in the gallery components, allowing for JavaScript execution when a visitor clicks the rendered link. This flaw is distinct from CVE-2026-33738, which addressed feed rendering. Defenders should prioritize verifying exposure and applying the patch, as the vulnerability allows for JavaScript execution in the Lychee origin, potentially leading to exposure of session data or enabled authenticated requests in the victim's context.

Defensive priority

Defenders should prioritize verifying exposure and applying the patch, as the vulnerability allows for JavaScript execution in the Lychee origin.

Recommended defensive actions

• Verify if the Lychee installation is prior to version 7.6.0 and apply the patch
• Restrict album-edit permissions to trusted users
• Monitor for suspicious activity in the Lychee origin
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed by the CVE Program record and the NVD vulnerability detail page. The issue is fixed in version 7.6.0. Defenders should verify if the Lychee installation is prior to version 7.6.0 and apply the patch. The vulnerability allows for JavaScript execution in the Lychee origin, potentially leading to exposure of session data or enabled authenticated requests in the victim's context. Evidence limits suggest verifying the Lychee version and configuration, particularly the allow_unsafe_links setting in config/mark

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.