NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

CVE-2021-39173 — cachet

HIGH

CVE-2021-39173 is a high-severity (CVSS 8.8) CWE-704 vulnerability in cachethq/cachet. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for cachethq/cachet — see the affected versions and patch details below.

Cachet vulnerable to forced reinstall

Also known asGHSA-r67m-m8c7-jp83
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘cachethq/cachet

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

Description

Impact

Authenticated users, regardless of their privileges (User or Admin), can trick Cachet and install the instance again, leading to arbitrary code execution on the server.

Patches

This issue was addressed by improving the middleware ReadyForUse, which now performs a stricter validation of the instance name.

Workarounds

Only allow trusted source IP addresses to access to the administration dashboard.

References

For more information

If you have any questions or comments about this advisory, you can contact:

  • The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
  • The maintainers, by opening an issue on this repository.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcachethq/cachetall versions2.5.1composer require cachethq/cachet:^2.5.1

Affected Products

1 product · 1 configurations
Application
catchetcatchethq
< 2.5.1
range
Exploits & PoCs
1

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 cachethq/cachet, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update cachethq/cachet to 2.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-39173 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.

Frequently Asked Questions

### Impact Authenticated users, regardless of their privileges (_User_ or _Admin_), can trick Cachet and install the instance again, leading to arbitrary code execution on the server. ### Patches This issue was addressed by improving the middleware `ReadyForUse`, which now performs a stricter validation of the instance name. ### Workarounds Only allow trusted source IP addresses to access to the administration dashboard. ### References - https://blog.sonarsource.com/cachet-code-execution-via-laravel-configuration-injection ### For more information If you have any questions or comment
O3 Security · Impact-Aware SCA

Is CVE-2021-39173 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2021-39173: cachet RCE — Fixed in 2.5.1