# CVE-2026-7017: HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets

> HTTP::Tiny leaks sensitive credentials to cross-origin redirect targets, allowing attackers to steal authentication tokens and cookies.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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:** Yes
- **Published:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-7017, ECHO-2e89-77f4-18bd, GHSA-pgc4-5jjm-7rr7, OESA-2026-3169, ROOT-OS-DEBIAN-11-CVE-2026-7017, UBUNTU-CVE-2026-7017, openSUSE-SU-2026:11219-1, openSUSE-SU-2026:21529-1

## What is CVE-2026-7017?

CVE-2026-7017 is a high-severity vulnerability in HAARG HTTP::Tiny, published on 7 Jul 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

HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.

When the server returns a 3xx redirect, `_maybe_redirect` follows the `Location:` header and `_prepare_headers_and_cb` re-merges the caller's `headers` argument into the new request, without checking whether the redirect target shares an origin with the original URL. Caller-supplied `Authorization`, `Cookie` and `Proxy-Authorization` headers are therefore re-sent to whatever host the redirect names, across scheme, host or port boundaries, and including `https` to `http` downgrades that expose them in plaintext on the wire.

The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-HTTP-Tiny` | openSUSE:Leap 16.0 | All versions | 0.096-bp160.1.1 |
| `perl-HTTP-Tiny` | openSUSE:Tumbleweed | All versions | 0.096-2.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-7017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7017 is a high-severity vulnerability in HAARG HTTP::Tiny, published on 7 Jul 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-7017 in the wild and no public exploit code.

Affected product: HAARG HTTP::Tiny. 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-7017/ (Markdown: https://insights.sbomify.com/CVE-2026-7017/index.md)
```

## Sources

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

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