Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-364c-vvqx-446c

HIGHFix: schollz/croc#697

GHSA-364c-vvqx-446c is a high-severity (CVSS 7.8) CWE-116 vulnerability in github.com/schollz/croc/v9. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-364c-vvqx-446c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Croc sender may place ANSI or CSI escape sequences in filename to attach receiver's terminal device

Also known asCVE-2023-43620GO-2023-2068
Published
Sep 20, 2023
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Feb 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/schollz/croc/v9

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in Croc before 9.6.16. A sender may place ANSI or CSI escape sequences in a filename to attack the terminal device of a receiver.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/schollz/croc/v9all versions9.6.16
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/schollz/croc/v9. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/schollz/croc/v9 to 9.6.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-364c-vvqx-446c is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-364c-vvqx-446c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-364c-vvqx-446c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Croc before 9.6.16. A sender may place ANSI or CSI escape sequences in a filename to attack the terminal device of a receiver.
O3 Security · Impact-Aware SCA

Is GHSA-364c-vvqx-446c in your dependencies?

O3 detects GHSA-364c-vvqx-446c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-364c-vvqx-446c: v9 (High 7.8) | O3 Security