# CVE-2026-48708: OliveTin has a Concurrent Template Parsing Race Condition which Leads to Cross-Request Command Contamination

> Concurrent template parsing in OliveTin allows cross-user command contamination and crashes, enabling unauthorized command execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-7fq5-7wr8-rjwj, GO-2026-5216

## What is CVE-2026-48708?

CVE-2026-48708 is a high-severity vulnerability in OliveTin, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OliveTin gives access to predefined shell commands from a web interface. In versions 3000.0.0 and prior, the template engine uses a single shared text/template.Template instance (tpl package-level variable in service/internal/tpl/templates.go) across all goroutines. Every action execution calls tpl.Parse(source) followed by t.Execute() on this shared instance with no synchronization. When two or more actions execute concurrently (which is the normal case — each ExecRequest spawns a goroutine), a race condition occurs: one goroutine's Parse overwrites the template tree while another goroutine is calling Execute, causing cross-user command contamination, Go runtime panic, and incorrect command execution. This issue has been resolved in version 3000.13.0.

Weakness: CWE-567 (Unsynchronized Access to Shared Data in a Multithreaded Context), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-48708?

3 open source packages ship an affected version, including github.com/OliveTin/OliveTin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260521225117-d74da9314005 |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260521225117-d74da9314005 |
| `github.com/OliveTin/OliveTin` | Go | All versions | 0.0.0-20260521225117-d74da9314005 |

## How do I fix CVE-2026-48708?

Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260521225117-d74da9314005 or later.

## Is CVE-2026-48708 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48708 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48708 and fix it if it is affected.

What it is: CVE-2026-48708 is a high-severity vulnerability in OliveTin, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48708 exists.

Affected packages and fixed versions:
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260521225117-d74da9314005
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260521225117-d74da9314005
- github.com/OliveTin/OliveTin (Go): affected all versions; fixed in 0.0.0-20260521225117-d74da9314005

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48708/ (Markdown: https://insights.sbomify.com/CVE-2026-48708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48708
- OSV: https://osv.dev/vulnerability/CVE-2026-48708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48708/
Summaries are generated and may contain mistakes; the official description above is the record.