Skip to main content
Vulnerability Database/CVE-2026-110225

CVE-2026-110225: Shaarli SSRF Vulnerability

CVE-2026-110225 is a server-side request forgery vulnerability in Shaarli through version 0.16.9 that lets authenticated users force the server to request internal addresses via bookmark thumbnails. This article covers the technical details, affected versions, security impact, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-110225 Overview

CVE-2026-110225 is a Server-Side Request Forgery (SSRF) vulnerability in Shaarli through version 0.16.9. The flaw resides in the thumbnail fetching logic, which does not validate the destination of bookmark URLs before issuing outbound HTTP requests. Authenticated users can create bookmarks that point to loopback, private, or cloud metadata endpoints and trigger the server to issue blind GET requests through the ThumbnailsController::ajaxUpdate route or on bookmark save. When Shaarli is configured in open_shaarli mode, any unauthenticated visitor can reach this functionality. The vulnerability maps to CWE-918: Server-Side Request Forgery.

Critical Impact

Attackers can coerce Shaarli to probe internal networks and cloud metadata services such as 169.254.169.254, potentially exposing instance credentials and internal service responses.

Affected Products

  • Shaarli bookmark manager through version 0.16.9
  • Shaarli instances running in open_shaarli public mode (reachable by any visitor)
  • Shaarli deployments hosted in cloud environments with Instance Metadata Service (IMDS) endpoints

Discovery Timeline

  • 2026-10-13 - CVE-2026-110225 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-110225

Vulnerability Analysis

Shaarli allows users to save bookmarks and automatically generate thumbnail previews of linked pages. The thumbnail retrieval component in application/Thumbnailer.php accepts the user-supplied URL and performs an outbound HTTP GET request to download preview content. The request logic does not enforce an address allow-list or reject private, loopback, link-local, or multicast ranges before resolution.

An authenticated attacker creates a bookmark whose URL targets an internal resource. Submitting the bookmark through the save path, or invoking the admin route ThumbnailsController::ajaxUpdate defined in application/front/controller/admin/ThumbnailsController.php, causes the Shaarli server to issue the request from its own network position. Because the response body is not returned to the attacker, this is a blind SSRF; however, timing, status codes, and side effects remain observable.

When the instance operates in open_shaarli mode, the saving flow is reachable without authentication, lowering the exploitation barrier to any network-adjacent visitor.

Root Cause

The thumbnailer component passes the raw bookmark URL to the HTTP client without performing private-address checks or hostname resolution filtering. There is no SSRF guard between the user-controlled input and the outbound socket.

Attack Vector

Exploitation requires network access to the Shaarli web interface and, in default mode, valid high-privilege credentials. The attacker creates or edits a bookmark with a URL pointing at http://127.0.0.1:<port>, http://10.0.0.0/8 ranges, or cloud metadata endpoints such as http://169.254.169.254/latest/meta-data/. Triggering ajaxUpdate or the save handler forces the server to perform the request. See the HackMD SSRF Vulnerability Analysis and the VulnCheck Shaarli SSRF Advisory for request-level details.

// No verified proof-of-concept code is published for CVE-2026-110225.
// Refer to the vendor source for the vulnerable call sites:
// - application/Thumbnailer.php (lines 82-98)
// - application/front/controller/admin/ThumbnailsController.php (lines 46-64)

Detection Methods for CVE-2026-110225

Indicators of Compromise

  • Outbound HTTP requests from the Shaarli host to RFC1918 ranges, 127.0.0.0/8, or 169.254.169.254 originating from the PHP process.
  • Shaarli web server access logs showing bookmark create, edit, or ajaxUpdate requests with URL parameters containing internal hostnames or private IP literals.
  • Unexpected metadata service queries in cloud provider flow logs tied to the Shaarli instance.

Detection Strategies

  • Inspect bookmark records in the Shaarli datastore for URLs targeting non-public destinations.
  • Correlate web request bursts to /admin/thumbnails or thumbnail update endpoints with outbound connections from the Shaarli service account.
  • Alert on Shaarli-originated DNS resolutions for internal zones or cloud metadata hostnames.

Monitoring Recommendations

  • Capture egress traffic from the Shaarli host and route it through a filtering proxy that logs destination IPs and hostnames.
  • Enable verbose logging on the Shaarli admin controller to record who invoked ThumbnailsController::ajaxUpdate and against which bookmark IDs.
  • In cloud deployments, enforce IMDSv2 and monitor for anomalous metadata access from the Shaarli workload.

How to Mitigate CVE-2026-110225

Immediate Actions Required

  • Disable the thumbnail feature in Shaarli configuration until a patched release is applied.
  • Disable open_shaarli public mode on any instance where unauthenticated users can trigger bookmark saves.
  • Restrict Shaarli egress at the network layer so the host cannot reach RFC1918 ranges, 127.0.0.0/8, or 169.254.169.254.

Patch Information

As of the NVD publication date, no fixed release is listed for Shaarli beyond version 0.16.9. Monitor the GitHub Shaarli Repository for an upstream patch that adds private-address validation inside Thumbnailer.php and the admin ThumbnailsController. Review the vulnerable code paths referenced in the Thumbnailer code snippet and the ThumbnailsController code snippet when assessing custom forks.

Workarounds

  • Place Shaarli behind a forward proxy that denies connections to private, loopback, link-local, and metadata address space.
  • Run Shaarli in an isolated network segment without routes to sensitive internal services or cloud metadata endpoints.
  • Enforce IMDSv2 on AWS workloads and require session tokens so blind GET-based SSRF cannot retrieve credentials.
  • Audit existing bookmarks and remove entries pointing to internal or metadata addresses before re-enabling thumbnails.
bash
# Example: disable thumbnails in Shaarli config/config.json.php
# "thumbnails": {
#     "enabled": false,
#     "width": 125,
#     "height": 90
# }

# Example: iptables egress restriction for the Shaarli host
iptables -A OUTPUT -d 127.0.0.0/8     -j REJECT
iptables -A OUTPUT -d 10.0.0.0/8      -j REJECT
iptables -A OUTPUT -d 172.16.0.0/12   -j REJECT
iptables -A OUTPUT -d 192.168.0.0/16  -j REJECT
iptables -A OUTPUT -d 169.254.0.0/16  -j REJECT

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.