{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2025-68686 in the wild since at least 27 Jul 2026.","fix":"No fix has been published for CVE-2025-68686 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Aug 2026.","what":"CVE-2025-68686 is a medium-severity vulnerability in Fortinet Fortios, published on 10 Feb 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-2025-68686 and fix it if it is affected.\n\nWhat it is: CVE-2025-68686 is a medium-severity vulnerability in Fortinet Fortios, published on 10 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-68686 in the wild since at least 27 Jul 2026.\n\nAffected product: Fortinet Fortios. 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-2025-68686/ (Markdown: https://insights.sbomify.com/CVE-2025-68686/index.md)","id":"CVE-2025-68686","markdown":"https://insights.sbomify.com/CVE-2025-68686/index.md","name":"CVE-2025-68686","record":{"aliases":["GHSA-839g-m33x-3w78"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiOS","requires_auth":"none","summary":"Remote attackers can bypass symbolic link persistence protections in FortiOS if they already have filesystem access, allowing continued unauthorized access.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortios","vendor":"fortinet"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An Exposure of Sensitive Information to an Unauthorized Actor vulnerability [CWE-200] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.1, FortiOS 7.4.0 through 7.4.6, FortiOS 7.2 all versions, FortiOS 7.0 all versions, FortiOS 6.4 all versions may allow a remote unauthenticated attacker to bypass the patch developed for the symbolic link persistency mechanism observed in some post-exploit cases, via crafted HTTP requests. An attacker would need first to have compromised the product via another vulnerability, at filesystem level.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2025-68686","indexable":true,"kev":{"dateAdded":"2026-07-27","dueDate":"2026-08-10","knownRansomwareCampaignUse":"Unknown","product":"FortiOS","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.","vendorProject":"Fortinet","vulnerabilityName":"Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortios","products":["fortinet:fortios"],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Not used","id":"CVE-2025-68687"},"packages":[],"prev":{"headline":"Apache Airflow: proxy credentials for various providers might leak in task logs","id":"CVE-2025-68675"},"products":["FortiOS"],"published":"2026-02-10","related":[{"cvss_score":9.8,"headline":"Fortinet Multiple Products Format String","id":"CVE-2024-23113","kev_date_added":"2024-10-09","published":"2024-02-15"},{"cvss_score":9.8,"headline":"Fortinet Multiple Products Authentication Bypass","id":"CVE-2022-40684","kev_date_added":"2022-10-11","published":"2022-10-18"},{"cvss_score":9.6,"headline":"Fortinet FortiOS and FortiProxy Authentication Bypass","id":"CVE-2024-55591","kev_date_added":"2025-01-14","published":"2025-01-14"},{"cvss_score":9.6,"headline":"Fortinet FortiOS Out-of-Bound Write","id":"CVE-2024-21762","kev_date_added":"2024-02-09","published":"2024-02-09"},{"cvss_score":9.3,"headline":"Fortinet FortiOS Heap-Based Buffer Overflow","id":"CVE-2022-42475","kev_date_added":"2022-12-13","published":"2023-01-02"},{"cvss_score":9.2,"headline":"Fortinet FortiOS and FortiProxy SSL-VPN Heap-Based Buffer Overflow","id":"CVE-2023-27997","kev_date_added":"2023-06-13","published":"2023-06-13"},{"cvss_score":9.1,"headline":"Fortinet Multiple Products Improper Verification of Cryptographic Signature","id":"CVE-2025-59718","kev_date_added":"2025-12-16","published":"2025-12-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["Fortinet"]},"summary":"Remote attackers can bypass symbolic link persistence protections in FortiOS if they already have filesystem access, allowing continued unauthorized access.","url":"https://insights.sbomify.com/CVE-2025-68686/"}