{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114069 exists.","fix":"No fix has been published for CVE-2026-114069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-114069 is a high-severity vulnerability in triggerdotdev trigger.dev, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-114069 and fix it if it is affected.\n\nWhat it is: CVE-2026-114069 is a high-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-114069 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-114069/ (Markdown: https://insights.sbomify.com/CVE-2026-114069/index.md)","id":"CVE-2026-114069","markdown":"https://insights.sbomify.com/CVE-2026-114069/index.md","name":"CVE-2026-114069","record":{"aliases":["GHSA-4gjx-f5hj-678x","GHSA-8jgj-f949-3f8m"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Trigger.dev before 4.6.0 contains an improper authorization vulnerability in the GET /api/v1/projects/:projectRef/envvars endpoint, which returns the environment's root API key as TRIGGER_SECRET_KEY for staging, production, and preview environments. Attackers holding a restricted read:envvars key can obtain the root secret and plaintext secrets, then trigger tasks and mint admin public JWTs.","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.6.0 Root Secret Disclosure via envvars API Endpoint","id":"CVE-2026-114069","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 4.5.0 before 4.6.0 Dashboard Agent User Token Disclosure via Session Records","id":"CVE-2026-114070"},"packages":[],"prev":{"headline":"Trigger.dev before 4.6.0 Missing Authorization via Waitpoint Token Wait Endpoint","id":"CVE-2026-114068"},"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":"total"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["triggerdotdev"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-114069/"}