Vulnerability in github.com/OliveTin/OliveTin (CVE-2026-48708)
Summary
Vulnerability in github.com/OliveTin/OliveTin (CVE-2026-48708). Successful exploitation can lead to full system takeover. Exploitable via tpl. Mitigation: upgrade to 0.0.0-20260521225117-d74da9314005 or later.
Original description
The description as published by the source.
Summary
OliveTin's 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: User A's arguments rendered in User B's shell command template
- Go runtime panic: Concurrent map writes in Go's
text/templateinternal structures cause a fatal crash - Incorrect command execution: Template/argument mismatch produces unexpected or dangerous shell commands
CWE
- CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)
- CWE-567 (Unsynchronized Access to Shared Data in a Multithreaded Context)
Affected Versions
- All versions (the shared template has existed since the template system was introduced)
Details
The Shared Template Instance
In service/internal/tpl/templates.go:
var tpl = template.New("tpl").
Option("missingkey=error").
Funcs(template.FuncMap{"Json": jsonFunc})
This is a package-level variable — a single *template.Template shared across the entire process.
Unsafe Parse…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48708 has been found in github.com/OliveTin/OliveTin.
Attackers can target a specific entry point like tpl over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade github.com/OliveTin/OliveTin to 0.0.0-20260521225117-d74da9314005 or later.
If unsure, ask your IT team or search "github.com/OliveTin/OliveTin CVE-2026-48708" on the vendor's site.
CVE-2026-48708 (github.com/OliveTin/OliveTin) — CWE-362 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: tpl / ExecRequest / Parse / Execute
Patched: 0.0.0-20260521225117-d74da9314005 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-362) exists in github.com/OliveTin/OliveTin. Attackers reach the vulnerable code path via tpl.
Check the vendor advisory for the affected versions of github.com/OliveTin/OliveTin. Attack surface: tpl / ExecRequest / Parse / Execute.
Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260521225117-d74da9314005.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/OliveTin/OliveTin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/OliveTin/OliveTin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/OliveTin/OliveTinを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/OliveTin/OliveTin to 0.0.0-20260521225117-d74da9314005ステージング環境で 0.0.0-20260521225117-d74da9314005 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com