{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-108267 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-108267 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-108267 is a critical vulnerability in Privasys go, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-108267 and fix it if it is affected.\n\nWhat it is: CVE-2026-108267 is a critical vulnerability in Privasys go, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-108267 in the wild and no public exploit code.\n\nAffected product: Privasys go. 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-108267/ (Markdown: https://insights.sbomify.com/CVE-2026-108267/index.md)","id":"CVE-2026-108267","markdown":"https://insights.sbomify.com/CVE-2026-108267/index.md","name":"CVE-2026-108267","record":{"aliases":["AZL-107973","AZL-107982","AZL-107985","AZL-107997","AZL-108006","GHSA-7jfw-53rm-phh2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go RA-TLS library","requires_auth":"none","summary":"Attackers can bypass remote attestation in Privasys Go by relaying quotes, allowing unverified connections to appear as attested enclaves.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Prior to privasys-v0.5.1-go1.26.5, challenge-mode RA-TLS certificates bound quote ReportData to the certificate public key and client nonce but not to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept a handshake terminated by the attacker as an attested enclave connection. This issue is fixed in privasys-v0.5.1-go1.26.5.","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 Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session","id":"CVE-2026-108267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"enclave-os-virtual: RA-TLS challenge certificates were not bound to the TLS session","id":"CVE-2026-108268"},"packages":[],"prev":{"headline":"Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session","id":"CVE-2026-108266"},"products":["go"],"published":"2026-10-09","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":"total"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["Privasys"]},"summary":"Attackers can bypass remote attestation in Privasys Go by relaying quotes, allowing unverified connections to appear as attested enclaves.","url":"https://insights.sbomify.com/CVE-2026-108267/"}