# CVE-2026-30118: Server-side request forgery in n/a

> Unauthenticated attackers can exploit SSRF in the Scalar Proxy endpoint to expose sensitive headers and potentially escalate privileges.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-46mr-vgx5-fc36

## What is CVE-2026-30118?

CVE-2026-30118 is a critical server-side request forgery vulnerability in n/a, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

scalar/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.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-30118 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30118 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30118 is a critical server-side request forgery vulnerability in n/a, published on 19 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30118 exists.

Affected product: n/a. 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-30118/ (Markdown: https://insights.sbomify.com/CVE-2026-30118/index.md)
```

## Sources

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

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