How severe is GHSA-4jc5-g844-4x33?

No CVSS score has been assigned to GHSA-4jc5-g844-4x33 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4jc5-g844-4x33?

GHSA-4jc5-g844-4x33 affects the following packages: linuxfabrik-lib (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-4jc5-g844-4x33?

Update linuxfabrik-lib to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jc5-g844-4x33 is resolved across your whole dependency graph.

How do I detect GHSA-4jc5-g844-4x33 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for linuxfabrik-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4jc5-g844-4x33 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4jc5-g844-4x33?

O3 pinpoints whether GHSA-4jc5-g844-4x33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4jc5-g844-4x33 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jc5-g844-4x33 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-4jc5-g844-4x33?

GHSA-4jc5-g844-4x33 is classified as Information Exposure (CWE-200), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-4jc5-g844-4x33 published, and has it been updated?

GHSA-4jc5-g844-4x33 was published on July 30, 2026 and was last updated on July 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-4jc5-g844-4x33

GHSA-4jc5-g844-4x33 is a Information Exposure vulnerability in linuxfabrik-lib. O3 Security confirms whether GHSA-4jc5-g844-4x33 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

linuxfabrik-lib: fetch() forwards credential headers across a cross-origin redirect

Also known asCVE-2026-67435

Published

Jul 30, 2026

Updated

Jul 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍linuxfabrik-lib

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

lib.url.fetch() follows HTTP redirects (follow_redirects=True). httpx strips only Authorization and Cookie when a redirect crosses the origin, so any other caller-supplied credential header (a session token such as Redfish's X-Auth-Token, an API key, ...) was still sent to the redirect target. A malicious or redirect-capable server can therefore answer an authenticated request with a 3xx to an attacker-chosen host and receive the credential (server-side request forgery + token disclosure). The pre-httpx urllib implementation was worse: it forwarded every header, including Authorization, across cross-host redirects.

Impact

Any plugin that authenticates to a host with a non-standard auth header and follows that host's redirects can be coerced into sending the credential, and an authenticated request, to another host the monitoring server can reach. The concrete case is the Redfish checks (X-Auth-Token), but the flaw is in the shared fetch() and affects every consumer.

Patches

Fixed in linuxfabrik-lib 6.0.0 (commit 6573ff9). On a cross-origin redirect (any scheme/host/port change other than a plain same-host HTTP-to-HTTPS upgrade) fetch() now keeps only benign transport headers and drops every other caller-supplied header, so credentials never follow a redirect to a different origin.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`linuxfabrik-lib`	all versions	6.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for linuxfabrik-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update linuxfabrik-lib to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jc5-g844-4x33 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4jc5-g844-4x33 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4jc5-g844-4x33. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary `lib.url.fetch()` follows HTTP redirects (`follow_redirects=True`). httpx strips only `Authorization` and `Cookie` when a redirect crosses the origin, so any other caller-supplied credential header (a session token such as Redfish's `X-Auth-Token`, an API key, ...) was still sent to the redirect target. A malicious or redirect-capable server can therefore answer an authenticated request with a `3xx` to an attacker-chosen host and receive the credential (server-side request forgery + token disclosure). The pre-httpx `urllib` implementation was worse: it forwarded every header, inclu

O3 Security · Impact-Aware SCA

Is GHSA-4jc5-g844-4x33 in your dependencies?

O3 detects GHSA-4jc5-g844-4x33 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works