CVE-2026-78038

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

build_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.

This issue affects ash_oban: from 0.2.5 before 0.8.14.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 30, 2026

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Aug 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit da2d81e1e8e1 (ash-project/ash_oban)

Patch available: ash-project/ash_oban v0.8.14 (contains commit da2d81e1e8e1)

https://github.com/ash-project/ash_oban/commit/da2d81e1e8e1dcc3e6ec8587cdb4f273575ffca3
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-78038
generic

CVE-2026-78038

https://cna.erlef.org/cves/CVE-2026-78038.html
github Patch Available🟡 PoC Available

Improper input handling in `AshOban.build_trigger/3` in AshOban lets `:args` override `primary_key`/`tenant`, allowing cross-tenant record retargeting · Advisory · ash-project/ash_oban · GitHub

https://github.com/ash-project/ash_oban/security/advisories/GHSA-gj9p-x393-rf9h

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_oban0.2.5 ... 0.8.9 (42 versions)0.8.14—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 07:18 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:13 UTCEG score recompute
  4. 2026-09-17 03:07 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 00:58 UTCEG score recompute
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-13 20:47 UTCEG score recompute
  11. 2026-09-12 18:42 UTCEG score recompute
  12. 2026-09-11 16:36 UTCEG score recompute
  13. 2026-09-10 14:31 UTCEG score recompute
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-09 12:26 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-08 10:20 UTCEG score recompute
  18. 2026-09-07 08:02 UTCEG score recompute
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-06 05:45 UTCEG score recompute
  21. 2026-09-05 03:40 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-01 17:34 UTCEG score recompute
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
Show 6 more
  1. 2026-09-01 04:40 UTCEPSS rescore
  2. 2026-08-31 15:29 UTCEG score recompute
  3. 2026-08-31 15:07 UTCEG score recompute
  4. 2026-08-30 12:29 UTCEG score recompute
  5. 2026-08-30 11:55 UTCEG score recompute
  6. 2026-08-30 11:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-78038?
CVE-2026-78038 is a medium vulnerability published on August 30, 2026. Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in ash-project ashoban allows a user whose input reaches the :args option of AshOban.buildtrigger/3 to retarget an update or destroy trigger at another record, including across tenants. buildtrigger/3…
When was CVE-2026-78038 disclosed?
CVE-2026-78038 was first published in the National Vulnerability Database on August 30, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78038 actively exploited?
CVE-2026-78038 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-78038?
CVE-2026-78038 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-78038?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78038, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78038

Explore →

Is Your Infrastructure Affected by CVE-2026-78038?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs