{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114074 exists.","fix":"No fix has been published for CVE-2026-114074 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114074 is a medium-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114074 and fix it if it is affected.\n\nWhat it is: CVE-2026-114074 is a medium-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114074 exists.\n\nAffected product: triggerdotdev trigger.dev. 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-114074/ (Markdown: https://insights.sbomify.com/CVE-2026-114074/index.md)","id":"CVE-2026-114074","markdown":"https://insights.sbomify.com/CVE-2026-114074/index.md","name":"CVE-2026-114074","record":{"aliases":["GHSA-27gg-p82j-765m","GHSA-fhh4-xvj5-m7pq"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Trigger.dev before 4.5.10 contains a server-side request forgery vulnerability that allows authenticated project members to bypass webhook SSRF protections by targeting the non-global 198.18.0.0/15 benchmarking range. Attackers can configure alert-channel webhooks pointing at internally routed services in this range, which isUnsafeIPv4 omits, to perform blind internal probing and limited state-changing POST requests.","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":"Trigger.dev before 4.5.10 Webhook SSRF Protection Bypass via 198.18.0.0/15 Range","id":"CVE-2026-114074","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Trigger.dev before 4.5.12 Authorization Bypass via Alert Channels API","id":"CVE-2026-114075"},"packages":[],"prev":{"headline":"Trigger.dev CLI before 4.5.9 Secret Exposure via Debug Deployment Logs","id":"CVE-2026-114073"},"products":["trigger.dev"],"published":"2026-10-21","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["triggerdotdev"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114074/"}