# CVE-2026-16637: OPeNDAP Hyrax SSRF and Credential Disclosure via Unvalidated Redirects

> Attackers can exploit unvalidated redirects in OPeNDAP Hyrax to perform SSRF and leak sensitive Earthdata authentication headers to external endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-7c9q-38r9-q62m

## What is CVE-2026-16637?

CVE-2026-16637 is a medium-severity server-side request forgery vulnerability in OPeNDAP Inc. hyrax-docker, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OPeNDAP Hyrax allows SSRF and credential disclosure via unvalidated HTTP redirects that bypass the AllowedHosts allowlist and leak Earthdata headers (User-Id, Echo-Token) to attacker-controlled endpoints.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-16637 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16637 is a medium-severity server-side request forgery vulnerability in OPeNDAP Inc. hyrax-docker, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-16637 in the wild and no public exploit code.

Affected product: OPeNDAP Inc. hyrax-docker. 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-16637/ (Markdown: https://insights.sbomify.com/CVE-2026-16637/index.md)
```

## Sources

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

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