Punk::OAuth2 versions before 0.03 for Perl allow an attacker-chosen off-site redirect after login...
Summary
Vulnerability reported (CVE-2026-75628). Confidential information can be exposed externally. Exploitable via evil.example.
Original description
The description as published by the source.
Punk::OAuth2 versions before 0.03 for Perl allow an attacker-chosen off-site redirect after login because same_origin_path accepts a backslash or tab in the return parameter.
oauth2_login reads the return parameter from the initiation request, runs same_origin_path over it, and stores the survivor in the session flow record as the post-login redirect target. That check rejects a value that does not begin with a slash, one with a slash as its second byte, and one containing CR or LF. A backslash and a tab pass. The URL Standard treats a backslash as equivalent to a slash for special schemes, so /\evil.example parses with the authority evil.example. It also strips ASCII tab before parsing, so a tab between two leading slashes leaves //evil.example.
A crafted link to the application's own login route lands the victim on the attacker's site after a genuine authentication. The redirect carries no authorization code or access token.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-75628 has been found.
Attackers can target a specific entry point like evil.example over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-75628" on the vendor's site.
CVE-2026-75628 — CWE-601 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: evil.example
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) has been reported. Attackers reach the vulnerable code path via evil.example.
Check the vendor advisory for the affected versions. Attack surface: evil.example.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web datatracker.ietf.org
- web metacpan.org
- web metacpan.org
- web url.spec.whatwg.org
- web url.spec.whatwg.org
- web nvd.nist.gov
- web openwall.com
- web github.com