{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76820 is a high-severity server-side request forgery vulnerability in OpenCTI-Platform opencti, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76820 and fix it if it is affected.\n\nWhat it is: CVE-2026-76820 is a high-severity server-side request forgery vulnerability in OpenCTI-Platform opencti, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76820 in the wild and no public exploit code.\n\nAffected product: OpenCTI-Platform opencti. 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-76820/ (Markdown: https://insights.sbomify.com/CVE-2026-76820/index.md)","id":"CVE-2026-76820","markdown":"https://insights.sbomify.com/CVE-2026-76820/index.md","name":"CVE-2026-76820","record":{"aliases":["GHSA-f6pj-3m32-q934"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenCTI threat intelligence","requires_auth":"low_privilege","summary":"Authenticated users can exploit missing URL validation in the synchronizer to access internal services and cloud metadata, enabling network scanning and data disclosure.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260701.0, the synchronizerFetch GraphQL query called fetchRemoteStreams after checking only that a remote stream URL used HTTP or HTTPS. The backend did not apply the ingestion deny list or reject private, loopback, and link-local destinations, allowing an authenticated account with the INGESTION capability to make OpenCTI request internal services and cloud metadata endpoints. Returned connection errors could distinguish open HTTP ports, open non-HTTP ports, and closed ports, enabling internal network scanning, while compatible endpoint responses could disclose internal data. This issue is fixed in version 7.260701.0.","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":"OpenCTI: Synchronizer SSRF: stream fetch has no URL validation","id":"CVE-2026-76820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenCTI: User-Controlled ReDoS in JSON Ingestion Mapper","id":"CVE-2026-76821"},"packages":[],"prev":{"headline":"Nuclei: Arbitrary Code Execution via Goja JavaScript Engine Vulnerability","id":"CVE-2026-76819"},"products":["opencti"],"published":"2026-09-15","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-09-16","vendors":["OpenCTI-Platform"]},"summary":"Authenticated users can exploit missing URL validation in the synchronizer to access internal services and cloud metadata, enabling network scanning and data disclosure.","url":"https://insights.sbomify.com/CVE-2026-76820/"}