CWE-362
Allowed-with-ReviewConcurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Abstraction: Class · Status: Draft
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
3773 vulnerabilities reference this CWE, most recent first.
GHSA-V256-34R4-J75Q
Vulnerability from github – Published: 2026-11-03 21:32 – Updated: 2026-11-03 21:32A race condition vulnerability exists in the API of HPE Networking Fabric Composer. Successful exploitation could allow an authenticated attacker with low privileges to corrupt the configuration state of the affected system.
{
"affected": [],
"aliases": [
"CVE-2026-95772"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-03T20:18:26Z",
"severity": "MODERATE"
},
"details": "A race condition vulnerability exists in the API of HPE Networking Fabric Composer. Successful exploitation could allow an authenticated attacker with low privileges to corrupt the configuration state of the affected system.",
"id": "GHSA-v256-34r4-j75q",
"modified": "2026-11-03T21:32:16Z",
"published": "2026-11-03T21:32:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-95772"
},
{
"type": "WEB",
"url": "https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05172en_us\u0026docLocale=en_US"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-V2J2-PH6R-WRG9
Vulnerability from github – Published: 2024-02-29 06:30 – Updated: 2025-01-13 18:31In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix race condition between session lookup and expire
Thread A + Thread B ksmbd_session_lookup | smb2_sess_setup sess = xa_load | | | xa_erase(&conn->sessions, sess->id); | | ksmbd_session_destroy(sess) --> kfree(sess) | // UAF! | sess->last_active = jiffies | +
This patch add rwsem to fix race condition between ksmbd_session_lookup and ksmbd_expire_session.
{
"affected": [],
"aliases": [
"CVE-2023-52480"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-29T06:15:46Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix race condition between session lookup and expire\n\n Thread A + Thread B\n ksmbd_session_lookup | smb2_sess_setup\n sess = xa_load |\n |\n | xa_erase(\u0026conn-\u003esessions, sess-\u003eid);\n |\n | ksmbd_session_destroy(sess) --\u003e kfree(sess)\n |\n // UAF! |\n sess-\u003elast_active = jiffies |\n +\n\nThis patch add rwsem to fix race condition between ksmbd_session_lookup\nand ksmbd_expire_session.",
"id": "GHSA-v2j2-ph6r-wrg9",
"modified": "2025-01-13T18:31:55Z",
"published": "2024-02-29T06:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52480"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/18ced78b0ebccc2d16f426143dc56ab3aad666be"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/53ff5cf89142b978b1a5ca8dc4d4425e6a09745f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a2ca5fd3dbcc665e1169044fa0c9e3eba779202b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c77fd3e25a51ac92b0f1b347a96eff6a0b4f066f"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V2X3-97GQ-36GP
Vulnerability from github – Published: 2022-05-17 03:39 – Updated: 2022-05-17 03:39Race condition in the ec_device_ioctl_xcmd function in drivers/platform/chrome/cros_ec_dev.c in the Linux kernel before 4.7 allows local users to cause a denial of service (out-of-bounds array access) by changing a certain size value, aka a "double fetch" vulnerability.
{
"affected": [],
"aliases": [
"CVE-2016-6156"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2016-08-06T20:59:00Z",
"severity": "MODERATE"
},
"details": "Race condition in the ec_device_ioctl_xcmd function in drivers/platform/chrome/cros_ec_dev.c in the Linux kernel before 4.7 allows local users to cause a denial of service (out-of-bounds array access) by changing a certain size value, aka a \"double fetch\" vulnerability.",
"id": "GHSA-v2x3-97gq-36gp",
"modified": "2022-05-17T03:39:45Z",
"published": "2022-05-17T03:39:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2016-6156"
},
{
"type": "WEB",
"url": "https://github.com/torvalds/linux/commit/096cdc6f52225835ff503f987a0d68ef770bb78e"
},
{
"type": "WEB",
"url": "https://bugzilla.kernel.org/show_bug.cgi?id=120131"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=1353490"
},
{
"type": "WEB",
"url": "http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=096cdc6f52225835ff503f987a0d68ef770bb78e"
},
{
"type": "WEB",
"url": "http://seclists.org/bugtraq/2016/Jul/20"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/91553"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V32F-C32X-PGFP
Vulnerability from github – Published: 2022-05-24 19:05 – Updated: 2025-10-22 00:32A use after free vulnerability via race condition in MFC charger driver prior to SMR MAY-2021 Release 1 allows arbitrary write given a radio privilege is compromised.
{
"affected": [],
"aliases": [
"CVE-2021-25394"
],
"database_specific": {
"cwe_ids": [
"CWE-362",
"CWE-416"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-06-11T15:15:00Z",
"severity": "MODERATE"
},
"details": "A use after free vulnerability via race condition in MFC charger driver prior to SMR MAY-2021 Release 1 allows arbitrary write given a radio privilege is compromised.",
"id": "GHSA-v32f-c32x-pgfp",
"modified": "2025-10-22T00:32:17Z",
"published": "2022-05-24T19:05:10Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25394"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com/securityUpdate.smsb?year=2021\u0026month=5"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-25394"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V3M7-X8GQ-MPP3
Vulnerability from github – Published: 2022-04-12 00:00 – Updated: 2022-04-19 00:01In vow, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is no needed for exploitation. Patch ID: ALPS05837742; Issue ID: ALPS05852812.
{
"affected": [],
"aliases": [
"CVE-2022-20077"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-11T20:15:00Z",
"severity": "MODERATE"
},
"details": "In vow, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is no needed for exploitation. Patch ID: ALPS05837742; Issue ID: ALPS05852812.",
"id": "GHSA-v3m7-x8gq-mpp3",
"modified": "2022-04-19T00:01:21Z",
"published": "2022-04-12T00:00:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-20077"
},
{
"type": "WEB",
"url": "https://corp.mediatek.com/product-security-bulletin/April-2022"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V3PH-CGQH-R8P5
Vulnerability from github – Published: 2026-10-15 20:14 – Updated: 2026-10-15 20:14Summary
In worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP's session extension is loaded as a shared module instead of being statically linked into the FrankenPHP binary. A request presenting Cookie: session=A can have session_id() resolve to B (a different concurrent client's id) or to a stale id from a previous request served by the same worker thread.
Impact
- Security: cross-user session exposure / session hijacking in worker mode. Same impact class as CVE-2026-24894.
- Functional: users are intermittently logged out; their cookie's session is ignored and they receive a foreign or empty session.
Affected / not affected
Exposure is determined by how the session extension is linked in the PHP build FrankenPHP is compiled against, not by the FrankenPHP release:
- Affected: any build where the
sessionextension is not visible to FrankenPHP at compile time, i.e. loaded as a shared / out-of-tree module (extension=sessionin an ini). This includes the RPM and Debian packages and other packagedphp-ztsdistributions that shipsessionas a shared extension underconf.d. - Not affected: builds where
sessionis statically compiled into the PHP that FrankenPHP links against, such as the official static binaries and Docker images. There, the reset code below is compiled in and clears the id every request.
The C session-reset code is unchanged across 1.11.x-1.12.x, so this is not a code regression between releases. A "1.12.2 works / 1.12.3 leaks" observation on the same host reflects two differently-built packages, not a source change. The persistent-zval helpers (#2366) are compiled only under FRANKENPHP_TEST and are unrelated.
Root cause
FrankenPHP resets per-request session state in frankenphp_reset_session_state(), which releases PS(id) so the next session_start() re-reads the request cookie. That whole function is guarded by #ifdef HAVE_PHP_SESSION, a macro defined only when the session extension headers are present at FrankenPHP compile time (session statically enabled in the PHP build). When session is a shared module, HAVE_PHP_SESSION is undefined, the reset is compiled out, and PS(id) survives the request boundary.
PHP's session_start() reads the request cookie only when PS(id) is NULL (ext/session/session.c, try_find_session_id_in_cookies(): if (!PS(use_cookies) || PS(id)) return;). With a stale PS(id), the cookie is ignored and the worker reuses the previous request's id, exposing it to whichever client is served next.
Reproduction
Minimal worker script (index.php):
<?php
$handler = static function () {
session_start();
$sent = $_COOKIE['session'] ?? '(none)';
$id = session_id();
header('Content-Type: text/plain');
echo ($sent === '(none)' || $sent === $id) ? "OK sent=$sent id=$id\n"
: "LEAK sent=$sent id=$id\n";
session_write_close();
};
while (\frankenphp_handle_request($handler)) {}
Run under worker mode with num 2 (≥2 workers), session.use_strict_mode=1, on a PHP build where session is a shared module. Pre-create two valid sessions A and B, then fire concurrent requests alternating the two cookies:
seq 600 | xargs -P32 -I{} sh -c '
c=$([ $(( {} % 2 )) -eq 0 ] && echo A || echo B);
curl -s -H "Cookie: session=$c" http://127.0.0.1:8080/' | grep -c LEAK
On an affected build a large fraction of responses are LEAK (session_id() differs from the cookie sent, and A and B sometimes resolve to the same id). On a statically-linked build the count is always 0.
Fix
When HAVE_PHP_SESSION is undefined, FrankenPHP now resets the session module through the module registry on every worker request (its RSHUTDOWN releases PS(id), RINIT re-initialises the globals), so the per-request cleanup always runs regardless of how the extension is linked. Statically-linked builds are unchanged and keep using frankenphp_reset_session_state().
Verified on PHP 8.6-dev ZTS, 2 workers, session.use_strict_mode=1, 600 alternating-cookie concurrent requests: before the fix 519/600 leaked; after the fix 0/600. Statically-linked builds stayed at 0/600.
Workarounds
- Use a FrankenPHP build with
sessionstatically compiled (official static binaries or Docker images). - Or, in the worker loop, after
session_write_close()callsession_id('')so the nextsession_start()re-reads the request cookie (withsession.use_strict_mode=1).
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.12.4"
},
"package": {
"ecosystem": "Go",
"name": "github.com/dunglas/frankenphp"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.12.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-82416"
],
"database_specific": {
"cwe_ids": [
"CWE-362",
"CWE-488"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-15T20:14:29Z",
"nvd_published_at": "2026-10-13T17:17:47Z",
"severity": "HIGH"
},
"details": "## Summary\nIn worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP\u0027s `session` extension is loaded as a shared module instead of being statically linked into the FrankenPHP binary. A request presenting `Cookie: session=A` can have `session_id()` resolve to `B` (a different concurrent client\u0027s id) or to a stale id from a previous request served by the same worker thread.\n\n## Impact\n- **Security:** cross-user session exposure / session hijacking in worker mode. Same impact class as CVE-2026-24894.\n- **Functional:** users are intermittently logged out; their cookie\u0027s session is ignored and they receive a foreign or empty session.\n\n## Affected / not affected\nExposure is determined by how the `session` extension is linked in the PHP build FrankenPHP is compiled against, **not** by the FrankenPHP release:\n\n- **Affected:** any build where the `session` extension is not visible to FrankenPHP at compile time, i.e. loaded as a shared / out-of-tree module (`extension=session` in an ini). This includes the RPM and Debian packages and other packaged `php-zts` distributions that ship `session` as a shared extension under `conf.d`.\n- **Not affected:** builds where `session` is statically compiled into the PHP that FrankenPHP links against, such as the official static binaries and Docker images. There, the reset code below is compiled in and clears the id every request.\n\nThe C session-reset code is unchanged across 1.11.x-1.12.x, so this is not a code regression between releases. A \"1.12.2 works / 1.12.3 leaks\" observation on the same host reflects two differently-built packages, not a source change. The persistent-zval helpers (#2366) are compiled only under `FRANKENPHP_TEST` and are unrelated.\n\n## Root cause\nFrankenPHP resets per-request session state in `frankenphp_reset_session_state()`, which releases `PS(id)` so the next `session_start()` re-reads the request cookie. That whole function is guarded by `#ifdef HAVE_PHP_SESSION`, a macro defined only when the session extension headers are present at FrankenPHP compile time (session statically enabled in the PHP build). When `session` is a shared module, `HAVE_PHP_SESSION` is undefined, the reset is compiled out, and `PS(id)` survives the request boundary.\n\nPHP\u0027s `session_start()` reads the request cookie only when `PS(id)` is `NULL` (`ext/session/session.c`, `try_find_session_id_in_cookies()`: `if (!PS(use_cookies) || PS(id)) return;`). With a stale `PS(id)`, the cookie is ignored and the worker reuses the previous request\u0027s id, exposing it to whichever client is served next.\n\n## Reproduction\nMinimal worker script (`index.php`):\n```php\n\u003c?php\n$handler = static function () {\n session_start();\n $sent = $_COOKIE[\u0027session\u0027] ?? \u0027(none)\u0027;\n $id = session_id();\n header(\u0027Content-Type: text/plain\u0027);\n echo ($sent === \u0027(none)\u0027 || $sent === $id) ? \"OK sent=$sent id=$id\\n\"\n : \"LEAK sent=$sent id=$id\\n\";\n session_write_close();\n};\nwhile (\\frankenphp_handle_request($handler)) {}\n```\nRun under worker mode with `num 2` (\u22652 workers), `session.use_strict_mode=1`, on a PHP build where `session` is a shared module. Pre-create two valid sessions `A` and `B`, then fire concurrent requests alternating the two cookies:\n```sh\nseq 600 | xargs -P32 -I{} sh -c \u0027\n c=$([ $(( {} % 2 )) -eq 0 ] \u0026\u0026 echo A || echo B);\n curl -s -H \"Cookie: session=$c\" http://127.0.0.1:8080/\u0027 | grep -c LEAK\n```\nOn an affected build a large fraction of responses are `LEAK` (`session_id()` differs from the cookie sent, and `A` and `B` sometimes resolve to the same id). On a statically-linked build the count is always `0`.\n\n## Fix\nWhen `HAVE_PHP_SESSION` is undefined, FrankenPHP now resets the `session` module through the module registry on every worker request (its `RSHUTDOWN` releases `PS(id)`, `RINIT` re-initialises the globals), so the per-request cleanup always runs regardless of how the extension is linked. Statically-linked builds are unchanged and keep using `frankenphp_reset_session_state()`.\n\nVerified on PHP 8.6-dev ZTS, 2 workers, `session.use_strict_mode=1`, 600 alternating-cookie concurrent requests: before the fix 519/600 leaked; after the fix 0/600. Statically-linked builds stayed at 0/600.\n\n## Workarounds\n- Use a FrankenPHP build with `session` statically compiled (official static binaries or Docker images).\n- Or, in the worker loop, after `session_write_close()` call `session_id(\u0027\u0027)` so the next `session_start()` re-reads the request cookie (with `session.use_strict_mode=1`).",
"id": "GHSA-v3ph-cgqh-r8p5",
"modified": "2026-10-15T20:14:29Z",
"published": "2026-10-15T20:14:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/security/advisories/GHSA-v3ph-cgqh-r8p5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82416"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/pull/2523"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/commit/be24d82531675f90862b8cde1e9fc7e9ee855aa5"
},
{
"type": "PACKAGE",
"url": "https://github.com/php/frankenphp"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/releases/tag/caddy/v1.12.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "FrankenPHP: Cross-request PHP session ID leak in worker mode when the session extension is a shared module"
}
GHSA-V3PH-G79M-WHJF
Vulnerability from github – Published: 2026-01-23 06:31 – Updated: 2026-01-23 06:31Anritsu ShockLine SCPI Race Condition Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Anritsu ShockLine. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the SCPI component. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27315.
{
"affected": [],
"aliases": [
"CVE-2025-15349"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-23T04:16:01Z",
"severity": "HIGH"
},
"details": "Anritsu ShockLine SCPI Race Condition Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Anritsu ShockLine. Authentication is not required to exploit this vulnerability.\n\nThe specific flaw exists within the SCPI component. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27315.",
"id": "GHSA-v3ph-g79m-whjf",
"modified": "2026-01-23T06:31:23Z",
"published": "2026-01-23T06:31:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15349"
},
{
"type": "WEB",
"url": "https://www.zerodayinitiative.com/advisories/ZDI-25-1200"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V3PW-85GV-XRJF
Vulnerability from github – Published: 2022-05-17 05:24 – Updated: 2025-01-21 21:30** DISPUTED ** Race condition in Dr.Web Security Space Pro 6.0.0.03100 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack. NOTE: this issue is disputed by some third parties because it is a flaw in a protection mechanism for situations where a crafted program has already begun to execute.
{
"affected": [],
"aliases": [
"CVE-2010-5159"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-08-25T21:55:00Z",
"severity": "MODERATE"
},
"details": "** DISPUTED ** Race condition in Dr.Web Security Space Pro 6.0.0.03100 on Windows XP allows local users to bypass kernel-mode hook handlers, and execute dangerous code that would otherwise be blocked by a handler but not blocked by signature-based malware detection, via certain user-space memory changes during hook-handler execution, aka an argument-switch attack or a KHOBE attack. NOTE: this issue is disputed by some third parties because it is a flaw in a protection mechanism for situations where a crafted program has already begun to execute.",
"id": "GHSA-v3pw-85gv-xrjf",
"modified": "2025-01-21T21:30:42Z",
"published": "2022-05-17T05:24:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-5159"
},
{
"type": "WEB",
"url": "http://archives.neohapsis.com/archives/bugtraq/2010-05/0026.html"
},
{
"type": "WEB",
"url": "http://archives.neohapsis.com/archives/fulldisclosure/2010-05/0066.html"
},
{
"type": "WEB",
"url": "http://countermeasures.trendmicro.eu/you-just-cant-trust-a-drunk"
},
{
"type": "WEB",
"url": "http://matousec.com/info/advisories/khobe-8.0-earthquake-for-windows-desktop-security-software.php"
},
{
"type": "WEB",
"url": "http://matousec.com/info/articles/khobe-8.0-earthquake-for-windows-desktop-security-software.php"
},
{
"type": "WEB",
"url": "http://www.f-secure.com/weblog/archives/00001949.html"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/67660"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/39924"
},
{
"type": "WEB",
"url": "http://www.theregister.co.uk/2010/05/07/argument_switch_av_bypass"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V3WG-FP7P-42JG
Vulnerability from github – Published: 2026-10-13 21:33 – Updated: 2026-10-13 21:33Use after free in Windows Storage allows an authorized attacker to elevate privileges locally.
{
"affected": [],
"aliases": [
"CVE-2026-69763"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-13T19:18:58Z",
"severity": "HIGH"
},
"details": "Use after free in Windows Storage allows an authorized attacker to elevate privileges locally.",
"id": "GHSA-v3wg-fp7p-42jg",
"modified": "2026-10-13T21:33:50Z",
"published": "2026-10-13T21:33:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-69763"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69763"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-V3WJ-CQ6J-489R
Vulnerability from github – Published: 2026-08-11 18:31 – Updated: 2026-08-11 18:31Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Telephony Service allows an authorized attacker to elevate privileges locally.
{
"affected": [],
"aliases": [
"CVE-2026-62734"
],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-11T17:18:24Z",
"severity": "HIGH"
},
"details": "Concurrent execution using shared resource with improper synchronization (\u0027race condition\u0027) in Windows Telephony Service allows an authorized attacker to elevate privileges locally.",
"id": "GHSA-v3wj-cq6j-489r",
"modified": "2026-08-11T18:31:17Z",
"published": "2026-08-11T18:31:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-62734"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62734"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Mitigation
Use thread-safe capabilities such as the data access abstraction in Spring.
Mitigation
- Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
- Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
Mitigation
When using multithreading and operating on shared variables, only use thread-safe functions.
Mitigation
Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.
Mitigation
Use a mutex if available, but be sure to avoid related weaknesses such as CWE-412.
Mitigation
Avoid double-checked locking (CWE-609) and other implementation errors that arise when trying to avoid the overhead of synchronization.
Mitigation
Disable interrupts or signals over critical parts of the code, but also make sure that the code does not go into a large or infinite loop.
Mitigation
Use the volatile type modifier for critical variables to avoid unexpected compiler optimization or reordering. This does not necessarily solve the synchronization problem, but it can help.
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
CAPEC-26: Leveraging Race Conditions
The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
CAPEC-29: Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.