Summary
OliveTin has Unvalidated ot_-prefixed Arguments that Bypass Input Filtering
Full technical description
Description
The filterToDefinedArgumentsOnly function in the executor is intended to discard any arguments not explicitly defined in the action's configuration. However, 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. - Included in the template context, available as
.Arguments.ot_*in template rendering.
Affected Code
Filter bypass, service/internal/executor/executor.go (lines 728–731):
func keepArgument(name string, definedNames map[string]struct{}) bool {
_, ok := definedNames[name]
return ok || strings.HasPrefix(name, "ot_")
}
System args only override two keys, service/internal/executor/executor.go (lines 742–745):
func injectSystemArgs(req *ExecutionRequest) {
req.Arguments["ot_executionTrackingId"] = req.TrackingID
req.Arguments["ot_username"] = req.AuthenticatedUser.Username
}
Any other ot_-prefixed argument (e.g., ot_malicious) survives both functions.
Unvalidated values become environment variables, service/internal/executor/executor.go (lines 867–882):
func buildEnv(args map[string]string) []string {
ret := append(os.Environ(), "OLIVETIN=1")
for k, v := range args {
varName := fmt.Sprintf("%v", strings.TrimSpace(strings.ToUpper(k)))
if varName == "" { continue }
ret = append(ret, fmt.Sprintf("%v=%v", varName, v))
}
return ret
}
The value v is never validated. It can contain newlines, shell metacharacters, null bytes, or any arbitrary data.
Proof of Concept
An attacker sends a StartAction request with extra ot_-prefixed arguments:
{
"bindingId": "<any-action-id>",
"arguments": [
{ "name": "ot_custom_var", "value": "arbitrary unvalidated content \n with newlines" },
{ "name": "ot_another", "value": "$(whoami)" }
]
}
These arguments:
- Pass through
filterToDefinedArgumentsOnly(theot_prefix exempts them). - Are never type-checked (not in the action's argument definitions).
- Become environment variables
OT_CUSTOM_VARandOT_ANOTHERin the executed command's environment. - Are available in the template rendering context as
.Arguments.ot_custom_varand.Arguments.ot_another.
Discovery Methodology
Both vulnerabilities were identified through manual source code review of the OliveTin repository, focusing on:
- Input validation boundaries (API request fields flowing into file system operations and execution contexts)
- Argument filtering and type-checking logic in the executor
- File path construction in the log persistence feature
No automated scanners or fuzzing tools were used. The review was conducted against the current main branch source code.
Impact
- Environment variable pollution, attacker can set arbitrary environment variables (with
OT_uppercased prefix) in the execution environment of any action they can trigger. Scripts or programs that read custom environment variables could be influenced. - Potential for secondary exploitation, if any executed script or command reads
OT_-prefixed environment variables, the unvalidated content could cause unexpected behavior. - Template context pollution, although Go's
text/templatedoes not recursively evaluate data values (mitigating direct template injection), the extra arguments are accessible in the template context and could interact unexpectedly with custom template logic.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2026-53541 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260531214440-ebffd9f040f7); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Remove the ot_ prefix exception from keepArgument, or restrict it to only the two known system arguments:
var systemArgs = map[string]struct{}{
"ot_executionTrackingId": {},
"ot_username": {},
}
func keepArgument(name string, definedNames map[string]struct{}) bool {
_, isDefined := definedNames[name]
_, isSystem := systemArgs[name]
return isDefined || isSystem
}
Frequently Asked Questions
- What is CVE-2026-53541? CVE-2026-53541 is a medium-severity improper input validation vulnerability in github.com/OliveTin/OliveTin (go), affecting versions < 0.0.0-20260531214440-ebffd9f040f7. It is fixed in 0.0.0-20260531214440-ebffd9f040f7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- How severe is CVE-2026-53541? CVE-2026-53541 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/OliveTin/OliveTin are affected by CVE-2026-53541? github.com/OliveTin/OliveTin (go) versions < 0.0.0-20260531214440-ebffd9f040f7 is affected.
- Is there a fix for CVE-2026-53541? Yes. CVE-2026-53541 is fixed in 0.0.0-20260531214440-ebffd9f040f7. Upgrade to this version or later.
- Is CVE-2026-53541 exploitable, and should I be worried? Whether CVE-2026-53541 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-53541 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-53541? Upgrade
github.com/OliveTin/OliveTinto 0.0.0-20260531214440-ebffd9f040f7 or later.