{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-6899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6899 is a medium-severity vulnerability in Systerel S2OPC, published on 9 Jun 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-6899 and fix it if it is affected.\n\nWhat it is: CVE-2026-6899 is a medium-severity vulnerability in Systerel S2OPC, published on 9 Jun 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-6899 in the wild and no public exploit code.\n\nAffected product: Systerel S2OPC. 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-6899/ (Markdown: https://insights.sbomify.com/CVE-2026-6899/index.md)","id":"CVE-2026-6899","markdown":"https://insights.sbomify.com/CVE-2026-6899/index.md","name":"CVE-2026-6899","record":{"aliases":["GHSA-j893-vcpr-rgfc"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"S2OPC OPC UA library","requires_auth":"none","summary":"Attackers can bypass certificate revocation checks in S2OPC by exploiting CRL handling flaws, allowing connections with revoked certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-299","name":"Improper Check for Certificate Revocation"}],"description":"Check for certificate revocation only considers the first matching CRL and ignores other valid CRLs of the same CA in the CycloneCrypto cryptographic wrapper of S2OPC library. It might allow connection between an OPC UA client and server using a revoked certificate.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Improper Check for Certificate Revocation in S2OPC","id":"CVE-2026-6899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Certificate Validation","id":"CVE-2026-6900"},"packages":[],"prev":{"headline":"Missing authorization in Wishlist Member","id":"CVE-2026-6898"},"products":["S2OPC"],"published":"2026-06-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":"partial"},"state":"PUBLISHED","updated":"2026-06-09","vendors":["Systerel"]},"summary":"Attackers can bypass certificate revocation checks in S2OPC by exploiting CRL handling flaws, allowing connections with revoked certificates.","url":"https://insights.sbomify.com/CVE-2026-6899/"}