{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-108361 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-108361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-108361 is a high-severity vulnerability in Privasys ra-tls-clients, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-108361 and fix it if it is affected.\n\nWhat it is: CVE-2026-108361 is a high-severity vulnerability in Privasys ra-tls-clients, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-108361 in the wild and no public exploit code.\n\nAffected product: Privasys ra-tls-clients. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-108361/ (Markdown: https://insights.sbomify.com/CVE-2026-108361/index.md)","id":"CVE-2026-108361","markdown":"https://insights.sbomify.com/CVE-2026-108361/index.md","name":"CVE-2026-108361","record":{"aliases":["GHSA-gg8q-mfhh-wrrc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TLS attestation library","requires_auth":"low_privilege","summary":"Local attackers can modify workload state after TLS attestation due to a TOCTOU race, bypassing security checks in Privasys ra-tls-clients.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"Privasys Remote Attestation TLS Clients provides multi-language utilities for verifying attested TLS connections. Before 0.9.1, an attacker with local access could modify workload code, data, and configuration at any time after successful connection establishment. Once Evidence was successfully appraised and the connection was established, there was a window of vulnerability from the establishment of the connection to the termination of the connection where an attacker could modify the state of the workload and platform at runtime on the TLS endpoint acting as the Attester. This vulnerability was possible because Privasys/ra-tls-clients performed attestation only once in the lifetime of the connection (at connection establishment time), and the verifying peer continued to believe that the state was the same as in the initial Evidence throughout, whereas it could be stale at some point in time. This vulnerability is fixed in 0.9.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privasys Intra-handshake attested TLS implementation is vulnerable to TOCTOU Attacks","id":"CVE-2026-108361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Privasys attested TLS accepted evidence from any unrevoked TEE platform (diversion attack)","id":"CVE-2026-108362"},"packages":[],"prev":{"headline":"PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading","id":"CVE-2026-108360"},"products":["ra-tls-clients"],"published":"2026-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Privasys"]},"summary":"Local attackers can modify workload state after TLS attestation due to a TOCTOU race, bypassing security checks in Privasys ra-tls-clients.","url":"https://insights.sbomify.com/CVE-2026-108361/"}