Loading vulnerability…
CVE-2026-1502 is a CRLF-injection vulnerability in Python's HTTP client. Proxy-tunnel headers and host values do not reject carriage-return and line-feed bytes, allowing attacker-controlled input to introduce additional information into HTTP communications. Potential consequences include HTTP response splitting and web-cache poisoning, depending on how downstream proxies and caches handle malformed requests. F5OS is affected; exact vulnerable Python and F5OS version ranges are not established.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A moderate-severity vulnerability tracked as CVE-2026-1502, covered by an AlmaLinux/TuxCare security update. The supplied CVSS vectors indicate integrity impact with high privileges and user interaction required under CVSS v3, but do not identify the affected component or flaw mechanism.
A vulnerability covered by the referenced AlmaLinux/TuxCare local security check; no technical flaw description is provided in the content.
A vulnerability referenced by the Rocky Linux 9.6 TuxCare local security-check advisory.
A moderate-severity vulnerability tracked as CVE-2026-1502. The supplied CVSS v3.0 vector indicates network attack vector, low attack complexity, required high privileges and user interaction, with integrity impact but no stated confidentiality or availability impact.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.