CVE-2026-0615
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Librarian `supervisord` status page can be retrieved by the `web_fetch` tool, which can be used to retrieve running processes within TheLibrarian backend. The vendor has fixed the vulnerability in all affected versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe web_fetch tool in TheLibrarian can access the internal supervisord status page, exposing running processes in the backend. This represents an information disclosure vulnerability where internal administrative interfaces are improperly accessible through the web_fetch functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm The Librarian installation existsIdentify if The Librarian application is installed in your environment. Check for the application binary or service named 'thelibrarian' or 'The Librarian'.Affected if The Librarian is installed and running in your environment.
-
Verify web_fetch tool is accessibleLocate and inspect the web_fetch functionality within The Librarian. This may be a CLI command, API endpoint, or configuration setting that enables HTTP fetching capabilities.Affected if The web_fetch tool is present and enabled in your The Librarian installation.
-
Test internal network access via web_fetchUse the web_fetch tool to attempt a request to an internal endpoint such as http://localhost:9001 (common supervisord port) or http://127.0.0.1. Check if the tool can retrieve internal administrative pages.Affected if The web_fetch tool can successfully retrieve content from internal URLs like localhost or 127.0.0.1 addresses.
-
Check for supervisord status exposureIf internal access is possible, attempt to access the supervisord status page (commonly at /_ping, /status, or similar admin paths on internal ports). Verify if running process information is returned.Affected if The web_fetch tool returns supervisord status information or reveals internal process details.
You are affected if The Librarian is installed with the web_fetch tool enabled and that tool can access internal endpoints, exposing administrative interfaces like supervisord status pages.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to the vendor-provided fixed versions. If immediate patching is not possible, restrict or disable the web_fetch tool's ability to access internal/admin endpoints.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data