VU#305509: OPeNDAP Hyrax is vulnerable to SSRF and Credential Disclosure
OPeNDAP Hyrax contains a Server Side Request Forgery (SSRF) vulnerability that allows an attacker to bypass the allowed hosts restriction via unvalidated HTTP redirects. This flaw can cause the application to communicate with unauthorized internal or external systems. Additionally, user authentication headers, including a legacy Echo-Token credential, may be leaked to attacker-controlled endpoints during these redirects. Exploitation could enable unauthenticated attackers to access internal services and, if a user is authenticated, disclose credentials that grant access to protected datasets. No official patch is confirmed yet, but a fix is expected in Hyrax version 1.18.0 or later. Administrators are advised to restrict gateway exposure to trusted networks until a patch is available.
AI Analysis
Technical Summary
CVE-2026-16637 affects OPeNDAP Hyrax, an open-source data server software for remote access to scientific datasets. The vulnerability arises because Hyrax follows HTTP 3xx redirects without verifying that the new destination is within the configured allowed hosts list. This allows an attacker to craft requests causing the server to connect to unauthorized or internal systems (SSRF). Furthermore, during such redirects, certain Earthdata user headers, including the User-Id and a legacy Echo-Token credential, are forwarded to the redirected destination, potentially leaking sensitive authentication information. The main authorization token is correctly stripped, but the legacy credential remains exposed. Successful exploitation can lead to unauthorized internal service access and credential disclosure. The CERT/CC notes no practical solution currently exists, but OPeNDAP is developing a patch expected in version 1.18.0 or later. Until then, administrators should carefully review allowed host configurations and limit gateway endpoint exposure to trusted networks.
Potential Impact
An unauthenticated remote attacker can exploit this vulnerability to perform SSRF attacks, accessing internal services that should not be reachable externally. If exploitation occurs while a user is authenticated, the attacker may obtain the user's Earthdata identifier and a reusable legacy credential (Echo-Token), enabling unauthorized access to protected datasets or resources as that user. This can lead to unauthorized data access and potential compromise of internal network resources.
Mitigation Recommendations
No official patch is confirmed as available yet; OPeNDAP is working on a fix expected in Hyrax version 1.18.0 or later. Until the patch is released, administrators should carefully review and tighten their allowed host configurations to prevent unauthorized redirects. Additionally, it is recommended to limit exposure of the Hyrax gateway endpoint to trusted networks only to reduce the attack surface.
VU#305509: OPeNDAP Hyrax is vulnerable to SSRF and Credential Disclosure
Description
OPeNDAP Hyrax contains a Server Side Request Forgery (SSRF) vulnerability that allows an attacker to bypass the allowed hosts restriction via unvalidated HTTP redirects. This flaw can cause the application to communicate with unauthorized internal or external systems. Additionally, user authentication headers, including a legacy Echo-Token credential, may be leaked to attacker-controlled endpoints during these redirects. Exploitation could enable unauthenticated attackers to access internal services and, if a user is authenticated, disclose credentials that grant access to protected datasets. No official patch is confirmed yet, but a fix is expected in Hyrax version 1.18.0 or later. Administrators are advised to restrict gateway exposure to trusted networks until a patch is available.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16637 affects OPeNDAP Hyrax, an open-source data server software for remote access to scientific datasets. The vulnerability arises because Hyrax follows HTTP 3xx redirects without verifying that the new destination is within the configured allowed hosts list. This allows an attacker to craft requests causing the server to connect to unauthorized or internal systems (SSRF). Furthermore, during such redirects, certain Earthdata user headers, including the User-Id and a legacy Echo-Token credential, are forwarded to the redirected destination, potentially leaking sensitive authentication information. The main authorization token is correctly stripped, but the legacy credential remains exposed. Successful exploitation can lead to unauthorized internal service access and credential disclosure. The CERT/CC notes no practical solution currently exists, but OPeNDAP is developing a patch expected in version 1.18.0 or later. Until then, administrators should carefully review allowed host configurations and limit gateway endpoint exposure to trusted networks.
Potential Impact
An unauthenticated remote attacker can exploit this vulnerability to perform SSRF attacks, accessing internal services that should not be reachable externally. If exploitation occurs while a user is authenticated, the attacker may obtain the user's Earthdata identifier and a reusable legacy credential (Echo-Token), enabling unauthorized access to protected datasets or resources as that user. This can lead to unauthorized data access and potential compromise of internal network resources.
Mitigation Recommendations
No official patch is confirmed as available yet; OPeNDAP is working on a fix expected in Hyrax version 1.18.0 or later. Until the patch is released, administrators should carefully review and tighten their allowed host configurations to prevent unauthorized redirects. Additionally, it is recommended to limit exposure of the Hyrax gateway endpoint to trusted networks only to reduce the attack surface.
Technical Details
- Classification
- {"confidence":0.83,"severitySource":"heuristic","classifier":"rss-v2"}
- Article Source
- {"url":"https://kb.cert.org/vuls/id/305509","fetched":true,"fetchedAt":"2026-08-04T13:00:01.898Z","wordCount":614}
Threat ID: 6a71e256bf8831d539d40d47
Added to database: 08/04/2026, 13:00:06 UTC
Last enriched: 08/04/2026, 13:00:22 UTC
Last updated: 08/04/2026, 13:00:22 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.