PatchTheCVECVE-2020-28437: This affects all versions of package heroku-env
CVE-2020-28437 is a critical-severity flaw (CVSS 9.4) affecting heroku-env. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
This affects all versions of package heroku-env. The injection point is located in lib/get.js which is required by index.js.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.4 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.3% (top 29%) |
| CISA exploited list | No |
| Weakness | CWE-77 |
| Published | 2022-08-02 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-28437?
heroku-env: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-28437 being exploited?
CVE-2020-28437 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-28437 affect?
CVE-2020-28437 affects heroku-env. Severity is critical (CVSS 9.4). This affects all versions of package heroku-env. The injection point is located in lib/get.js which is required by index.js.
How urgent is CVE-2020-28437?
Priority 61/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action