How severe is CVE-2026-78319?

CVE-2026-78319 has a CVSS 4.0 base score of 9.3, rated critical severity.

Is CVE-2026-78319 being actively exploited?

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

How do I fix CVE-2026-78319?

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

When was CVE-2026-78319 published?

CVE-2026-78319 was published on 2026-09-01 and last updated on 2026-09-03.

CVE-2026-78319

CVE-2026-78319 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.3. 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-367.

Key facts

Severity: Critical (CVSS 4.0 base score 9.3)
EPSS exploit prediction: 1% (47th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-367
Published: 2026-09-01
Last modified: 2026-09-03

Description

A service running on the affected products contains a potential Time-of-Check Time-of-Use (TOCTOU) race condition. An unauthenticated remote attacker could exploit this race condition to bypass intended security controls. This may result in the execution of unauthorized code.

Frequently asked questions

What is CVE-2026-78319?: A service running on the affected products contains a potential Time-of-Check Time-of-Use (TOCTOU) race condition. An unauthenticated remote attacker could exploit this race condition to bypass intended security controls. This may result in the execution of unauthorized code.
How severe is CVE-2026-78319?: CVE-2026-78319 has a CVSS 4.0 base score of 9.3, rated critical severity.
Is CVE-2026-78319 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-78319?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-78319 published?: CVE-2026-78319 was published on 2026-09-01 and last updated on 2026-09-03.

References

Other CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) vulnerabilities

CVE-2026-25641 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.29, there is a sandbox escape vulnerability due to a…
CVE-2025-64180 — Critical (CVSS 10.0): Manager-io/Manager is accounting software. In Manager Desktop and Server versions 25.11.1.3085 and below, a critical…
CVE-2026-68488 — Critical (CVSS 9.9): A Time-of-check Time-of-use (TOCTOU) race condition leading to insecure symlink following in Plesk causes local…
CVE-2026-63297 — Critical (CVSS 9.9): An authorization bypass vulnerability in LXD due to a timing flaw during configuration merging allows an authenticated…
CVE-2026-25052 — Critical (CVSS 9.9): n8n is an open source workflow automation platform. Prior to versions 1.123.18 and 2.5.0, a vulnerability in the file…
CVE-2025-13032 — Critical (CVSS 9.9): Double fetch in sandbox kernel driver in Avast/AVG Antivirus <25.3 on windows allows local attacker to escalate…

Browse all CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition) vulnerabilities →