# CVE-2026-66773: Server-controlled `__next` URL is not checking cross-origin

> A malicious OData service can exploit an unchecked server-controlled URL to disclose sensitive authentication information and inject untrusted data.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-hc5j-q32w-c25v, GHSA-wj2g-hp6v-8wj4

## What is CVE-2026-66773?

CVE-2026-66773 is a medium-severity vulnerability in SAP_SE Odata, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A malicious or compromised OData service could disclose sensitive authentication information and inject untrusted data into the application, which may leads to a high impact on confidentiality and low impact on integrity and no impact on Availability.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-66773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66773 is a medium-severity vulnerability in SAP_SE Odata, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66773 in the wild and no public exploit code.

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

## Sources

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

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