{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33126 exists.","fix":"No fix has been published for CVE-2026-33126 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33126 is a medium-severity server-side request forgery vulnerability in blakeblackshear frigate, published on 20 Mar 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-33126 and fix it if it is affected.\n\nWhat it is: CVE-2026-33126 is a medium-severity server-side request forgery vulnerability in blakeblackshear frigate, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33126 exists.\n\nAffected product: blakeblackshear frigate. 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-33126/ (Markdown: https://insights.sbomify.com/CVE-2026-33126/index.md)","id":"CVE-2026-33126","markdown":"https://insights.sbomify.com/CVE-2026-33126/index.md","name":"CVE-2026-33126","record":{"aliases":["GHSA-j6g3-3j3q-c2xv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Network Video Recorder","requires_auth":"low_privilege","summary":"An attacker can exploit the /ffprobe endpoint to perform Server-Side Request Forgery, accessing internal resources or cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"frigate","vendor":"frigate"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Frigate is a network video recorder (NVR) with realtime local object detection for IP cameras. Prior to version 0.16.3, the /ffprobe endpoint accepts arbitrary user-controlled URLs without proper validation, allowing Server-Side Request Forgery (SSRF) attacks. An attacker can use the Frigate server to make HTTP requests to internal network resources, cloud metadata services, or perform port scanning. This issue has been patched in version 0.16.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Frigate has SSRF vulnerability in /ffprobe endpoint","id":"CVE-2026-33126","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"h3 has a Server-Sent Events Injection via Unsanitized Newlines in Event Stream Fields","id":"CVE-2026-33128"},"packages":[],"prev":{"headline":"Frigate Broken Access Control: Users assigned the viewer role can delete admin and other low-privileged accounts","id":"CVE-2026-33125"},"products":["frigate"],"published":"2026-03-20","related":[{"cvss_score":9.1,"headline":"Frigate Affected by Authenticated Remote Command Execution (RCE) and Container Escape","id":"CVE-2026-25643","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":8.6,"headline":"Frigate has insecure password change functionality","id":"CVE-2026-33124","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"Frigate cross-site request forgery in `config_save` and `config_set` request handlers","id":"CVE-2023-45670","kev_date_added":null,"published":"2023-10-30"},{"cvss_score":7.5,"headline":"Frigate unsafe deserialization in `load_config_with_no_duplicates` of `frigate/util/builtin.py`","id":"CVE-2023-45672","kev_date_added":null,"published":"2023-10-30"},{"cvss_score":7.1,"headline":"Frigate Broken Access Control: Users assigned the viewer role can delete admin and other low-privileged accounts","id":"CVE-2026-33125","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":6.5,"headline":"Authenticated Frigate users can read the full unredacted configuration via `/api/config/raw","id":"CVE-2026-33469","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":6.5,"headline":"Missing authorization in frigate","id":"CVE-2026-33470","kev_date_added":null,"published":"2026-03-26"}],"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":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-25","vendors":["blakeblackshear"]},"summary":"An attacker can exploit the /ffprobe endpoint to perform Server-Side Request Forgery, accessing internal resources or cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-33126/"}