dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-15508

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 · unedited
A flaw has been found in Helicone ai-gateway up to 0.2.0-beta.30. This affects the function build_target_url of the file ai-gateway/src/dispatcher/service.rs of the component AWS Metadata Service. Executing a manipulation of the argument extracted_path_and_query can lead to server-side request forgery. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

Helicone ai-gateway contains a server-side request forgery (SSRF) vulnerability in the build_target_url function within the AWS Metadata Service component. By manipulating the extracted_path_and_query argument, an attacker can cause the application to make arbitrary requests to internal or external resources, potentially accessing the AWS metadata service at 169.254.169.254 to exfiltrate credentials.

MitigationImplement strict input validation and allowlist filtering on the extracted_path_and_query parameter to prevent manipulation of the target URL. Additionally, block access to metadata endpoints (169.254.169.254) at the network level.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Helicone ai-gateway installation
    Search for Helicone files in the environment, typically installed via npm package 'helicone' or Docker container with 'helicone' image name. Check package.json dependencies or container listings.
    Affected if Helicone ai-gateway package is present in the environment
  2. Check application version
    Locate the installed version by running 'npm list helicone' if using npm, or check the Docker image tag. Compare against the version that contains the build_target_url function in the AWS Metadata Service component.
    Affected if The installed version contains the vulnerable AWS Metadata Service code (no specific safe version range provided)
  3. Verify AWS Metadata Service component is active
    Inspect the codebase for usage of the AWS Metadata Service, typically found in files handling AWS credential retrieval or metadata endpoint access. Look for imports or references to metadata service logic.
    Affected if The application uses AWS Metadata Service for credential retrieval and that component is enabled
  4. Inspect build_target_url function for extracted_path_and_query handling
    Search source code for the build_target_url function within the AWS Metadata Service module. Examine how the extracted_path_and_query parameter is processed and whether it allows arbitrary URL manipulation.
    Affected if The function does not validate or sanitize the extracted_path_and_query parameter before using it in URL construction
  5. Check network accessibility to metadata endpoint
    Verify if the environment allows outbound access to 169.254.169.254 (AWS metadata IP). This can be checked via firewall rules, security groups, or network policies.
    Affected if The application server can reach 169.254.169.254 and the vulnerable code path is exercisable

The environment is affected if Helicone ai-gateway with the vulnerable build_target_url function is installed, the AWS Metadata Service component is enabled, and network access to 169.254.169.254 is permitted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and allowlist filtering on the extracted_path_and_query parameter to prevent manipulation of the target URL. Additionally, block access to metadata endpoints (169.254.169.254) at the network level.

Recommended fix Moderate confidence

Latest stable release after 0.2.0-beta.30

  1. Upgrade Helicone ai-gateway to a version beyond 0.2.0-beta.30 (e.g., the latest stable release)
  2. After upgrading, verify the fix by testing that requests to the AWS Metadata Service endpoint (169.254.169.254) are no longer possible through the build_target_url function
  3. Confirm that the extracted_path_and_query parameter is now properly validated/sanitized before being used in URL construction
Caveat Check release notes for any breaking changes between 0.2.0-beta.30 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15508 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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