CVE-2026-30118
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 · uneditedscalar/astro v0.1.13 was discovered to contain a Server-Side Request Forgery (SSRF) in the scalar_url query parameter of the Scalar Proxy endpoint. This vulnerability allows unauthenticated attackers to force the backend server to send HTTP requests to attacker-controlled URLs, leading to authentication cookies and headers exposure and possible privilege escalation.
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 confidencescalar/astro v0.1.13 contains an unauthenticated SSRF vulnerability in the scalar_url query parameter of the Scalar Proxy endpoint. Attackers can supply arbitrary URLs causing the server to make requests to attacker-controlled destinations, potentially exposing internal authentication cookies and headers sent in proxied requests.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed scalar/astro versionRun a version check command for the scalar/astro package (e.g., check package.json, node_modules, or use package manager commands like npm list scalar/astro or pip show scalar-astro depending on the installation method)Affected if The installed version is v0.1.13 or falls within the affected range based on the summary (scalar/astro v0.1.13)
-
Confirm Scalar Proxy endpoint is exposedIdentify whether the application exposes the /scalar-proxy or similar proxy endpoint. Check application routing configuration, OpenAPI spec, or attempt a HEAD/GET request to known proxy paths (e.g., /scalar/api/proxy, /api/scalar-proxy)Affected if The Scalar Proxy endpoint is accessible and responds to requests
-
Verify scalar_url parameter acceptanceSend a test request to the proxy endpoint with a scalar_url query parameter pointing to an internal or controlled URL (e.g., http://localhost or http://127.0.0.1) and observe if the server attempts to fetch itAffected if The endpoint accepts the scalar_url parameter and attempts to resolve arbitrary URLs provided in it
-
Inspect proxy configuration settingsReview application configuration files (e.g., config files, environment variables, scalar/astro configuration) for proxy-related settings or endpointsAffected if Proxy functionality is enabled in the configuration
A user is affected if they are running scalar/astro v0.1.13 (or an affected version) with the Scalar Proxy endpoint exposed and the scalar_url query parameter accepting 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 allowlist validation for the scalar_url parameter, disable the proxy functionality if not required, or upgrade to a patched version if available. Consider network segmentation to limit outbound request capabilities.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30118 — 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-30118 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