CVE-2026-31817: GO-2026-4670 - OliveTin's unsafe parsing of UniqueTrackingId can be used to write files in github.com/OliveTin/OliveTin

CVE-2026-31817 · Severity: low · CVSS 3.1 · Published 2026-03-12

OliveTin's unsafe parsing of UniqueTrackingId can be used to write files in github.com/OliveTin/OliveTin

Technologies: github.com/OliveTin/OliveTin (Go). Vendors: Go.

Quick answers

Is CVE-2026-31817 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-31817 being exploited in the wild.
How severe is CVE-2026-31817?
Low severity, with a CVSS score of 3.1, published 12 March 2026.
Which products and versions are affected?
github.com/OliveTin/OliveTin (Go) SEMVER:introduced=0,fixed=0.0.0-20260309102040-b03af0e2eca3.
Is there a fix for CVE-2026-31817?
Yes. github.com/OliveTin/OliveTin (Go): upgrade to 0.0.0-20260309102040-b03af0e2eca3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-31817?
Check whether you run github.com/OliveTin/OliveTin (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/OliveTin/OliveTin (Go): upgrade to 0.0.0-20260309102040-b03af0e2eca3 or later
    go get github.com/OliveTin/OliveTin@v0.0.0-20260309102040-b03af0e2eca3

Affected products

  • github.com/OliveTin/OliveTin (Go) SEMVER:introduced=0,fixed=0.0.0-20260309102040-b03af0e2eca3

Identifiers

  • CVE-2026-31817
  • GHSA-364q-w7vh-vhpc
  • GO-2026-4670

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.