CVE-2026-31817
Directory traversal in OliveTin StartAction API allows arbitrary file write.
Is CVE-2026-31817 being exploited?
Not confirmed. CVE-2026-31817 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-31817?
CVE-2026-31817 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-31817?
Yes. A fix has been recorded for CVE-2026-31817. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-31817 affect?
CVE-2026-31817 affects OliveTin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-31817?
Apply 3000.11.2 patch.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can write files to arbitrary filesystem locations via unvalidated UniqueTrackingId in StartAction API; risk of payload placement/overwrite.
Patch when possible
- affected< 3000.11.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.