CVE-2026-105263 Shaarli CVE debrief

Who should care

Defenders responsible for Shaarli installations should assess exposure and prioritize upgrading to version 0.16.4 to mitigate this vulnerability. This includes IT administrators, security teams, and operators managing Shaarli deployments. They should verify the presence of vulnerable versions, review system logs for potential exploitation attempts, and ensure that compensating controls are in place for exposed systems. Upgrading to version 0.16.4 is a key

Why it matters

Defenders should care about CVE-2026-105263 because it allows remote attackers to perform server-side request forgery on Shaarli installations up to version 0.16.3, potentially leading to unauthorized access, data breaches, or server compromise. Verification of exposure and upgrading to version 0.16.4 are crucial.

• Potential unauthorized access to internal resources
• Possible data breaches through SSRF
• Risk of server compromise through exploitation
• Need for verification of Shaarli installation exposure

Technical summary

The MetadataController function in Shaarli's Admin Metadata Endpoint is vulnerable to server-side request forgery (SSRF) due to improper handling of the url argument. This allows remote attackers to manipulate the server into making unintended requests, potentially leading to unauthorized access, data breaches, or server compromise. The vulnerability exists in Shaarli versions up to 0.16.3 and is fixed in version 0.16.4. Defenders should prioritize verifying exposure and upgrading vulnerable installations to mitigate this risk.

Defensive priority

Defenders should prioritize verifying exposure of Shaarli installations to this vulnerability and upgrading to version 0.16.4 if vulnerable.

Recommended defensive actions

• Verify Shaarli installations for exposure to this vulnerability
• Upgrade vulnerable Shaarli installations to version 0.16.4
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the available patch. Defenders should verify Shaarli installations for exposure, focusing on versions up to 0.16.3, and prioritize upgrading to version 0.16.4. Evidence from the CVE Program and NVD suggests that this SSRF vulnerability can be exploited remotely, potentially leading to unauthorized access or data breaches. Further verification is necessary to confirm the extent of exposure and ensure proper mitigation.

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.