CVE-2026-53541

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-64203 (ENISA EUVD) · GHSA-prj9-97mp-mwh2 (GitHub Security Advisories) · GO-2026-5552 (OSV.dev)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

OliveTin gives access to predefined shell commands from a web interface. The filterToDefinedArgumentsOnly function in the executor is intended to discard any arguments not explicitly defined in the action's configuration. However, prior to commit ebffd9f040f791208aee1db2e5a8aecd1e3e603d, a special case allows any argument whose name starts with ot_ to bypass this filter. While two system arguments (ot_executionTrackingId and ot_username) are injected by OliveTin and overridden, all other ot_-prefixed arguments supplied by the user pass through unmodified. These bypassed arguments are not type-checked — the validation loop only iterates over the action's defined arguments, so ot_-prefixed arguments skip all type safety checks entirely; set as environment variables — via buildEnv(), with completely unvalidated values, and passed to the executed command; and included in the template context — available as .Arguments.ot_* in template rendering. Commit ebffd9f040f791208aee1db2e5a8aecd1e3e603d contains a patch.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 24, 2026

Last Modified

October 14, 2026

Advisory Details (2)

Auto-updated Aug 21, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit ebffd9f040f7 (OliveTin/OliveTin)

Fix landed in OliveTin/OliveTin commit ebffd9f040f7 — awaiting tagged release

https://github.com/OliveTin/OliveTin/commit/ebffd9f040f791208aee1db2e5a8aecd1e3e603d
GitHub advisoryMentions a patch (unverified)

Unvalidated `ot_`-prefixed Arguments Bypass Input Filtering · Advisory · OliveTin/OliveTin · GitHub

https://github.com/OliveTin/OliveTin/security/advisories/GHSA-prj9-97mp-mwh2

Vendor Advisories for CVE-2026-53541(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/OliveTin/OliveTin—
  • every version up to 0.0.0-20260531214440-ebffd9f040f7: fixed in 0.0.0-20260531214440-ebffd9f040f7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-27 13:55 UTCOSV refresh
  3. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-10-25 14:20 UTCEG score recompute
  6. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-18 03:31 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-14 19:35 UTCEG score recompute
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-14 01:24 UTCOSV refresh
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-12 15:57 UTCEG score recompute
  23. 2026-10-11 19:40 UTCEG score recompute
  24. 2026-10-11 16:55 UTCEG score recompute
  25. 2026-10-11 14:19 UTCEG score recompute
Show 54 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-09-23 09:52 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-09-18 07:49 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-09-14 01:34 UTCEG score recompute
  26. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-09-12 16:09 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  30. 2026-09-09 22:59 UTCEG score recompute
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  35. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-08-30 19:51 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-08-28 03:05 UTCEG score recompute
  43. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  46. 2026-08-24 20:29 UTCEG score recompute
  47. 2026-08-24 20:12 UTCEG score recompute
  48. 2026-08-23 01:17 UTCEG score recompute
  49. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-08-21 23:28 UTCEG score recompute
  51. 2026-07-31 04:22 UTCEG score recompute
  52. 2026-07-26 15:26 UTCEG score recompute
  53. 2026-07-23 03:19 UTCEG score recompute
  54. 2026-06-24 18:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53541?
CVE-2026-53541 is a medium-severity vulnerability; its CVE record was published on June 24, 2026. OliveTin gives access to predefined shell commands from a web interface. The filterToDefinedArgumentsOnly function in the executor is intended to discard any arguments not explicitly defined in the action's configuration. However, prior to commit ebffd9f040f791208aee1db2e5a8aecd1e3e603d, a special…
When was the CVE record for CVE-2026-53541 published?
The CVE record for CVE-2026-53541 was published on June 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-53541 actively exploited?
CVE-2026-53541 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53541?
CVE-2026-53541 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53541?
A fix for CVE-2026-53541 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53541 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53541?

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