Summary
generated automatically from NVD dataMISP versions up to 2.5.45 insufficiently validate outbound HTTP destinations in feed retrieval and TAXII discovery. Feed redirects were followed without checking scheme or destination, so feed credentials could be forwarded to another host and internal network resources reached via SSRF. The TAXII discovery check relied on gethostbyname() and a few literal addresses, missing ::1 and encodings like 0x7f000001. The CVSS v3.1 score is 9.1 (CRITICAL).
NVD description
Affected versions of MISP contain insufficient validation of server-side outbound HTTP destinations in feed retrieval and TAXII discovery functionality. In feed processing, redirects were followed without validating the redirect scheme or destination. The original request headers were reused across redirect hops, meaning authentication headers or API credentials configured for a feed could be forwarded to a different host. Redirects could also target internal network resources, resulting in SSRF. The fix adds redirect validation, blocks internal destinations for cross-host redirects, strips configured feed credentials before following redirects to another host, and pins validated DNS results to prevent re-resolution after validation. The TAXII discovery endpoint had a related incomplete SSRF defense. It used gethostbyname() and compared the result against only a few literal addresses. This missed cases including IPv6 loopback (::1), numeric host encodings such as 0x7f000001, and potentially multiple DNS records. The fix moves TAXII discovery to the shared URL egress validator. Together, these commits harden MISP's outbound URL handling against alternate-address representations, DNS-related bypasses, unsafe redirects, internal-host access, and cross-host credential forwarding. Version affected: ≤2.5.45
EPSS · FIRST.org
0.42%probability of exploitation in the next 30 days
Higher than 34% of scored CVEs
EPSS (Exploit Prediction Scoring System) estimates, from observed exploitation activity, how likely a CVE is to be exploited in the next 30 days. It complements CVSS, which measures severity, not likelihood. Score of 2026-10-16, recomputed daily by FIRST.org.
In-depth analysis on cveo.tech
We've published a detailed analysis of this CVE — exploitation, IOCs and mitigation.
CVSS v3.1 Score
Information
- Published
- 7 sept. 2026
- Updated
- 9 sept. 2026
- Status
- Analyzed
- Source
- 5a6e4751-2f3f-4070-9419-94fb35b644e8
Affected products
Weaknesses (CWE)
References (2)
Similar CVEs
Other vulnerabilities of type CWE-200
Monitor your products
Get automatic alerts for every new CVE affecting your equipment.