How severe is CVE-2026-109346?

CVE-2026-109346 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-109346 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-109346?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-109346 published?

CVE-2026-109346 was published on 2026-10-12 and last updated on 2026-10-16.

CVE-2026-109346

CVE-2026-109346 is a high-severity vulnerability with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-451.

Key facts

Severity: High (CVSS 3.x base score 8.1)
CVSS v4: 8.5
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-451
Published: 2026-10-12
Last modified: 2026-10-16

Description

better-auth from 1.3.8-beta.3 before 1.7.0-rc.3 contains a UI misrepresentation vulnerability in the deviceAuthorization plugin because GET /device omits the requesting client_id and scope. Attackers can start a device request via /device/code, trick signed-in users into approving the code, then redeem it at /device/token for a live session token.

Frequently asked questions

What is CVE-2026-109346?: better-auth from 1.3.8-beta.3 before 1.7.0-rc.3 contains a UI misrepresentation vulnerability in the deviceAuthorization plugin because GET /device omits the requesting client_id and scope. Attackers can start a device request via /device/code, trick signed-in users into approving the code, then redeem it at /device/token for a live session token.
How severe is CVE-2026-109346?: CVE-2026-109346 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-109346 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-109346?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-109346 published?: CVE-2026-109346 was published on 2026-10-12 and last updated on 2026-10-16.

References

Other CWE-451 vulnerabilities

CVE-2026-2634 — Critical (CVSS 9.8): Malicious scripts could cause desynchronization between the address bar and web content before a response is received…
CVE-2026-0907 — Critical (CVSS 9.8): Incorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform UI…
CVE-2026-0906 — Critical (CVSS 9.8): Incorrect security UI in Google Chrome on Android prior to 144.0.7559.59 allowed a remote attacker to spoof the…
CVE-2025-8043 — Critical (CVSS 9.8): Focus incorrectly truncated URLs towards the beginning instead of around the origin. This vulnerability was fixed in…
CVE-2026-11175 — High (CVSS 8.8): Incorrect security UI in Messages in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to…
CVE-2026-11172 — High (CVSS 8.8): Incorrect security UI in Contact Picker in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to…

Browse all CWE-451 vulnerabilities →