# CVE-2026-0612: CVE-2026-0612

> Attackers can exploit the web_fetch tool to proxy requests and leak information via The Librarian infrastructure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2026
- **Updated:** 16 Jan 2026
- **Also known as:** GHSA-vhwm-c99c-xhcp

## What is CVE-2026-0612?

CVE-2026-0612 is a high-severity server-side request forgery vulnerability in TheLibrarian.io, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Librarian contains a information leakage vulnerability through the `web_fetch` tool, which can be used to retrieve arbitrary external content provided by an attacker, which can be used to proxy requests through The Librarian infrastructure. The vendor has fixed the vulnerability in all versions of TheLibrarian.

## Which versions are affected by CVE-2026-0612?

It affects 1 product.


Products: Thelibrarian the Librarian.

## How do I fix CVE-2026-0612?

No fix has been published for CVE-2026-0612 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0612 being exploited?

There is no known exploitation of CVE-2026-0612 in the wild and no public exploit code.

## Other vulnerabilities in TheLibrarian.io

- [CVE-2026-0613](https://insights.sbomify.com/CVE-2026-0613/): CVE-2026-0613 (high 7.5)
- [CVE-2026-0616](https://insights.sbomify.com/CVE-2026-0616/): CVE-2026-0616 (high 7.5)
- [CVE-2026-0615](https://insights.sbomify.com/CVE-2026-0615/): CVE-2026-0615 (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0612 and fix it if it is affected.

What it is: CVE-2026-0612 is a high-severity server-side request forgery vulnerability in TheLibrarian.io, published on 16 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0612 in the wild and no public exploit code.

Affected product: TheLibrarian.io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0612/ (Markdown: https://insights.sbomify.com/CVE-2026-0612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0612
- OSV: https://osv.dev/vulnerability/CVE-2026-0612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0612/
Summaries are generated and may contain mistakes; the official description above is the record.
