Skip to main content
VulnerabilityPublished

CVE-2026-0612: TheLibrarian.io · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects TheLibrarian.ioSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
TheLibrarianTheLibrarian.ioAffected
  • <=1.0
Fixed in–

AI-suggested

  1. Immediately apply the vendor-provided patches for TheLibrarian.io to all affected systems to remediate the vulnerability.
  2. Restrict network access to the web_fetch tool by implementing firewall rules or network segmentation to limit exposure to trusted users or systems only.
  3. Monitor network traffic and application logs for unusual proxying behavior or unexpected external content retrieval patterns that may indicate exploitation attempts.
  4. Employ web application firewalls (WAFs) with rules designed to detect and block malicious use of URL parameters in the web_fetch functionality.
  5. Conduct regular security assessments and penetration tests focusing on content retrieval features to identify similar weaknesses.
  6. Educate development and operations teams about the risks of proxying external content without proper validation or access controls.
  7. Where feasible, disable or limit the use of web_fetch functionality if it is not essential to business operations.
  8. Implement strict input validation and output encoding in any custom integrations with TheLibrarian.io to prevent abuse. These measures, combined with patching, will reduce the likelihood of successful exploitation and limit the potential impact of this vulnerability.

Description

CVE-2026-0612 is a high-severity information leakage vulnerability in TheLibrarian.io's web_fetch tool that allows attackers to retrieve arbitrary external content via the platform, effectively proxying requests through TheLibrarian infrastructure. This flaw exposes sensitive system information to unauthorized parties without requiring authentication or user interaction. The vulnerability impacts confidentiality but does not affect integrity or availability. Although no known exploits are reported in the wild, the ease of exploitation and network accessibility make it a significant risk. The vendor has released patches for all versions, and organizations using TheLibrarian.io should apply updates immediately. European organizations relying on TheLibrarian.io for content retrieval or proxying services are at risk of data exposure and potential indirect attacks. Countries with higher adoption of TheLibrarian.

References

Community reviews

Loading reviews…