CVE-2026-41713
Stored input can influence model behavior across turns.
Is CVE-2026-41713 being exploited?
Not confirmed. CVE-2026-41713 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.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-41713?
CVE-2026-41713 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-41713?
Yes. A fix has been recorded for CVE-2026-41713. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41713 affect?
CVE-2026-41713 affects Advisor platform with user-controlled input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41713?
Patch when released; sanitize inputs; limit memory retention.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored input can steer model responses across turns, enabling manipulation of behavior or output.
Patch when possible
- affected>= 1.0.0 and < 1.0.7
- affected>= 1.1.0 and < 1.1.6
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.