CVE-2026-71847
High-severity unknown vulnerability CVE-2026-71847; investigate and harden systems.
Is CVE-2026-71847 being exploited?
Not confirmed. CVE-2026-71847 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-71847?
CVE-2026-71847 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71847?
Yes. A fix has been recorded for CVE-2026-71847. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71847 affect?
CVE-2026-71847 affects Unknown (vendor/product details pending). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71847?
Isolate suspicious hosts, increase logging/IDS, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Likely enables remote code execution or full system compromise, permitting unauthorized code execution, data theft, and persistence.
Immediate action required
- affected>= 2.20.0 and < 2.21.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.