CVE-2026-9372
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 · uneditedA flaw has been found in ItzCrazyKns Vane up to 1.12.1. This vulnerability affects unknown code of the file src/app/api/providers/route.ts of the component Model Provider API. This manipulation of the argument baseURL causes server-side request forgery. Remote exploitation of the attack is possible. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
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 · high confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the ItzCrazyKns Vane project, specifically in the Model Provider API route (src/app/api/providers/route.ts). The baseURL parameter is not properly validated, allowing attackers to manipulate it to make the server fetch arbitrary internal or external resources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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.
-
Identify the application versionLocate the package.json or version file for the ItzCrazyKns Vane installation and record the version numberAffected if The installed version is 1.12.1 or earlier (any version up to and including 1.12.1)
-
Locate the vulnerable API endpoint fileSearch for the file src/app/api/providers/route.ts in the application source codeAffected if The file exists in the codebase, indicating the vulnerable endpoint is present
-
Verify the API endpoint is accessibleCheck if the /api/providers route is exposed and reachable (e.g., curl http://localhost:3000/api/providers or check route configuration)Affected if The endpoint is accessible via HTTP/HTTPS and accepts requests
-
Confirm baseURL parameter handlingInspect the route.ts file to see if the baseURL query parameter is validated against an allowlist or rejected for untrusted domainsAffected if The code does NOT validate or restrict the baseURL parameter to trusted domains only (the parameter passes unsanitized to fetch/node-fetch)
-
Test for SSRF susceptibilitySend a request to the /api/providers endpoint with a baseURL pointing to an internal resource (e.g., http://127.0.0.1:port or http://169.254.169.254) and observe if the server makes the requestAffected if The server successfully retrieves content from the provided URL, confirming the SSRF vulnerability is exploitable
A user is affected if they run ItzCrazyKns Vane version 1.12.1 or earlier AND the /api/providers endpoint is exposed AND the baseURL parameter is not validated against a trusted allowlist, allowing the server to be directed to arbitrary URLs.
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 dataImplement strict URL allowlist validation for the baseURL parameter in the affected API route, ensuring only trusted endpoints can be requested. Additionally, add network segmentation and disable unnecessary outbound connections from the server.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9372 — 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-9372 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