Advisory record · GHSA-xfjj-f699-rc79

tiagorlampert CHAOS vulnerable to arbitrary code execution

CVSS 9.8 CriticalCriticalEPSS 0.014 · 72nd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 7 May 2024, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/tiagorlampert/CHAOSGo<0.0.0-20220716132853-b47438d36e3a0.0.0-20220716132853-b47438d36e3a
Identifiers
GHSA-xfjj-f699-rc79 · CVE-2024-30850 · CVE-2024-33434 · GHSA-p3j6-f45h-hw5f · GO-2024-2822
Weakness (CWE)
CWE-78
Published
7 May 2024
Updated
6 Apr 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

github.com/tiagorlampert/CHAOS before 0.0.0-20220716132853-b47438d36e3a is vulnerable to arbitrary code execution. A remote attacker can exploit unsanitized handling of the filename argument to run code. Upgrade to 0.0.0-20220716132853-b47438d36e3a or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.014, the 72nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.