CVE-2026-41713

High
8.2
0.05.010.0
Year
2026
Published
May 12, 2026
Known Affected Devices
0
CVSS Score
8.2

What is CVE-2026-41713?

A malicious user could craft input that is stored in conversation memory and later interpreted by the model in an unintended way. Applications using the affected advisor with user-controlled input may be susceptible to manipulation of model behavior across conversation turns.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
AV
Attack Vector
Network

Exploitable remotely over the network without requiring access to the local system.

AC
Attack Complexity
Low

No special conditions required. Exploit can be performed reliably and repeatedly.

PR
Privileges Required
None

No authentication required. Any anonymous user can exploit this vulnerability.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
Low

Some sensitive information is disclosed, but attacker has limited access.

I
Integrity Impact
High

Complete loss of integrity. Attacker can modify any file or data on the component.

A
Availability Impact
None

No availability impact. Service remains fully operational.

FAQ

How severe is CVE-2026-41713?

CVE-2026-41713 has a CVSS score of 8.2/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.

What does the CVSS score mean for CVE-2026-41713?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-41713 scores 8.2/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2026-41713?

The list of devices confirmed to be affected by CVE-2026-41713 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2026-41713?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.