{"answers":{"affected":"1 open source package ship an affected version, including ash_oban.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78038 exists.","fix":"Upgrade ash_oban to 0.8.14 or later.","what":"CVE-2026-78038 is a medium-severity missing authorization vulnerability in ash-project ash_oban, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-78038 and fix it if it is affected.\n\nWhat it is: CVE-2026-78038 is a medium-severity missing authorization vulnerability in ash-project ash_oban, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78038 exists.\n\nAffected packages and fixed versions:\n- ash_oban (Hex): affected from 0.2.5; fixed in 0.8.14\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-78038/ (Markdown: https://insights.sbomify.com/CVE-2026-78038/index.md)","id":"CVE-2026-78038","markdown":"https://insights.sbomify.com/CVE-2026-78038/index.md","name":"CVE-2026-78038","record":{"aliases":["EEF-CVE-2026-78038","GHSA-gj9p-x393-rf9h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir background job library","requires_auth":"none","summary":"Attackers can bypass tenant isolation and authorization controls by injecting arguments into AshOban triggers, allowing unauthorized modification of records across tenants.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"}],"description":"Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in ash-project ash_oban allows a user whose input reaches the :args option of AshOban.build_trigger/3 to retarget an update or destroy trigger at another record, including across tenants.\n\nbuild_trigger/3 builds the trusted job arguments with atom keys (:primary_key, :tenant, :action_arguments) and merges the caller's :args underneath so the trusted values win on collision. Because Oban job arguments round-trip through JSON, the caller's keys arrive as strings, so Map.merge sees no collision and both keys survive. When the job is persisted the JSON object is de-duplicated keeping the last (string) key, and the worker reads the caller's value. The documentation describes :args as unable to affect the action, so an application that forwards user input into it for uniqueness scoping is exposed to authorization bypass and tenant isolation breaks.\n\nThis issue affects ash_oban: from 0.2.5 before 0.8.14.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Job argument injection via :args overrides primary_key and tenant in AshOban","id":"CVE-2026-78038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Path traversal in OpenVPN","id":"CVE-2026-78043"},"packages":[{"ecosystem":"Hex","fixed":["0.8.14"],"introduced":["0.2.5"],"last_affected":[],"package":"ash_oban","purl":"pkg:hex/ash_oban","source":"EEF-CVE-2026-78038"}],"prev":{"headline":"Xiiaozet LK100W OS Command Injection","id":"CVE-2026-78037"},"products":["ash_oban"],"published":"2026-08-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"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-08-31","vendors":["ash-project"]},"summary":"Attackers can bypass tenant isolation and authorization controls by injecting arguments into AshOban triggers, allowing unauthorized modification of records across tenants.","url":"https://insights.sbomify.com/CVE-2026-78038/"}