Skip to main content
CVE-2026-7017VulnerabilityPublished Updated

SUSE · Security update for perl-HTTP-Tiny

Affects SUSESource GCVE Database

0
Compare
Authoritative record:CVE-2026-7017· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade SUSE HTTP-Tiny to 0.095 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.095
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade HTTP::Tiny and HTTP-Tiny to 0.095.

Affected software

ProductAffectedFixed in
HAARGHTTP::TinyAffected
  • <0.095
Fixed in
  • 0.095
GitHubHTTP-Tinypkg:github/HTTP-TinyOther threatsAffected
  • <0.095
Fixed in
  • 0.095

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for perl-HTTP-Tiny fixes the following issues: Changes in perl-HTTP-Tiny: - updated to 0.096 - CVE-2026-7017: Fixed forwarded credential headers to cross-origin redirect targets (bsc#1271020) - Caller-supplied Authorization, Cookie, and Proxy-Authorization headers are now stripped on cross-origin redirects by default. Use allow_credentialed_redirects to opt out. - Redirects are no longer automatically followed when going from https to http. Use allow_downgrade to revert to the original behaviour.

References

Community reviews

Loading reviews…