Loading vulnerability…
CVE-2025-5025 is an improper certificate validation vulnerability in libcurl's HTTPS certificate public-key pinning support. When libcurl uses the wolfSSL TLS backend and connects over QUIC for HTTP/3, it omits the configured server public-key pin verification. Consequently, a transfer configured to require a pinned public key can complete without verifying that pin when HTTP/3 is negotiated.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a Proof-of-Concept (PoC) environment for CVE-2025-5025, focusing on HTTP/3 (QUIC) and TLS certificate handling. The structure consists of Dockerfiles for a client and two servers (real and fake), orchestrated via docker-compose. The client container builds curl with HTTP/3 and wolfSSL support, and the servers use Python's aioquic library to provide HTTP/3 endpoints with custom certificates. The docker-compose file sets up a private network with static IPs and mounts certificate files into the containers. The PoC is designed to demonstrate or test the vulnerability scenario described by CVE-2025-5025, likely involving certificate pinning or validation bypasses between the client and the two servers. No direct exploit payload is present; the repository provides an environment to reproduce or analyze the 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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.