CVE-2021-21423

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 1.4% (71st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

projen is a project generation tool that synthesizes project configuration files such as package.json, tsconfig.json, .gitignore, GitHub Workflows, eslint, jest, and more, from a well-typed definition written in JavaScript. Users of projen's NodeProject project type (including any project type derived from it) include a .github/workflows/rebuild-bot.yml workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the "main" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the "main" repository. The rebuild-bot workflow is triggered by comments including @projen rebuild on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an issue_comment event, and thus always executes with a GITHUB_TOKEN belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by pull_request events, which always execute with a GITHUB_TOKEN belonging to the repository from which the pull-request is made). Repositories that do not have branch protection configured on their default branch (typically main or master) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed GITHUB_TOKEN would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
36
EG Risk 36/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
71st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 6, 2021

Last Modified

November 21, 2024

References (6)

Affected Packages

(2 across 2 ecosystems)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
projen—
  • 0.6.0 up to 0.16.41: fixed in 0.16.41
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
projen0.14.0 ... 0.16.9 (70 versions)
  • every version up to 0.16.41: fixed in 0.16.41
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:39 UTCEPSS rescore
  3. 2026-10-07 23:44 UTCEPSS rescore
  4. 2026-10-06 15:13 UTCEPSS rescore
  5. 2026-10-05 17:40 UTCEPSS rescore
  6. 2026-10-04 23:18 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-10-03 14:22 UTCEPSS rescore
  9. 2026-10-02 16:22 UTCEPSS rescore
  10. 2026-10-01 19:46 UTCEPSS rescore
  11. 2026-09-30 15:29 UTCEG score recompute
  12. 2026-09-30 15:00 UTCEPSS rescore
  13. 2026-09-28 13:47 UTCEPSS rescore
  14. 2026-09-27 13:41 UTCEPSS rescore
  15. 2026-09-26 15:54 UTCEPSS rescore
  16. 2026-09-26 15:54 UTCEPSS rescore
  17. 2026-09-26 04:45 UTCOSV refresh
  18. 2026-09-26 00:21 UTCEPSS rescore
  19. 2026-09-24 14:00 UTCEPSS rescore
  20. 2026-09-24 14:00 UTCEPSS rescore
  21. 2026-09-23 13:44 UTCEPSS rescore
  22. 2026-09-22 14:44 UTCEPSS rescore
  23. 2026-09-21 20:28 UTCEPSS rescore
  24. 2026-09-19 15:37 UTCEPSS rescore
  25. 2026-09-18 19:23 UTCEPSS rescore
Show 75 more
  1. 2026-09-17 19:23 UTCEPSS rescore
  2. 2026-09-16 14:05 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-15 03:06 UTCEPSS rescore
  5. 2026-09-13 16:43 UTCEPSS rescore
  6. 2026-09-12 14:57 UTCEPSS rescore
  7. 2026-09-11 09:33 UTCEPSS rescore
  8. 2026-09-10 09:29 UTCEPSS rescore
  9. 2026-09-08 21:56 UTCEPSS rescore
  10. 2026-09-07 15:58 UTCEPSS rescore
  11. 2026-09-06 19:31 UTCOSV refresh
  12. 2026-09-06 13:44 UTCEPSS rescore
  13. 2026-09-06 13:44 UTCEPSS rescore
  14. 2026-09-05 15:25 UTCEPSS rescore
  15. 2026-09-04 13:57 UTCEPSS rescore
  16. 2026-09-04 05:03 UTCEPSS rescore
  17. 2026-09-02 14:08 UTCEPSS rescore
  18. 2026-09-01 13:50 UTCEPSS rescore
  19. 2026-09-01 03:32 UTCEPSS rescore
  20. 2026-08-30 19:14 UTCEPSS rescore
  21. 2026-08-30 01:19 UTCEPSS rescore
  22. 2026-08-28 21:37 UTCEPSS rescore
  23. 2026-08-27 14:22 UTCEPSS rescore
  24. 2026-08-26 14:42 UTCEPSS rescore
  25. 2026-08-25 13:45 UTCEPSS rescore
  26. 2026-08-23 00:16 UTCEPSS rescore
  27. 2026-08-21 23:46 UTCEPSS rescore
  28. 2026-08-20 22:52 UTCEPSS rescore
  29. 2026-08-20 05:34 UTCOSV refresh
  30. 2026-08-19 17:01 UTCEPSS rescore
  31. 2026-08-18 13:45 UTCEPSS rescore
  32. 2026-08-17 13:43 UTCEPSS rescore
  33. 2026-08-16 14:52 UTCEPSS rescore
  34. 2026-08-16 02:11 UTCEPSS rescore
  35. 2026-08-15 01:27 UTCEPSS rescore
  36. 2026-08-13 21:57 UTCEPSS rescore
  37. 2026-08-12 13:47 UTCEPSS rescore
  38. 2026-08-11 13:38 UTCEPSS rescore
  39. 2026-08-09 13:43 UTCEPSS rescore
  40. 2026-08-08 16:33 UTCEPSS rescore
  41. 2026-08-07 16:23 UTCEPSS rescore
  42. 2026-08-06 13:43 UTCEPSS rescore
  43. 2026-08-05 19:14 UTCEPSS rescore
  44. 2026-08-05 00:40 UTCOSV refresh
  45. 2026-08-04 15:06 UTCEPSS rescore
  46. 2026-08-04 10:34 UTCEPSS rescore
  47. 2026-08-03 10:32 UTCEPSS rescore
  48. 2026-08-02 02:24 UTCEPSS rescore
  49. 2026-08-01 04:12 UTCEPSS rescore
  50. 2026-07-30 16:25 UTCEPSS rescore
  51. 2026-07-30 01:27 UTCEPSS rescore
  52. 2026-07-30 01:27 UTCEPSS rescore
  53. 2026-07-26 14:52 UTCEPSS rescore
  54. 2026-07-25 14:15 UTCEPSS rescore
  55. 2026-07-24 14:15 UTCEPSS rescore
  56. 2026-07-23 14:15 UTCEPSS rescore
  57. 2026-07-23 01:57 UTCEG score recompute
  58. 2026-07-22 22:43 UTCEG score recompute
  59. 2026-07-22 14:05 UTCEPSS rescore
  60. 2026-07-21 15:22 UTCEPSS rescore
  61. 2026-07-21 15:22 UTCEPSS rescore
  62. 2026-07-20 17:04 UTCEPSS rescore
  63. 2026-07-19 14:28 UTCEPSS rescore
  64. 2026-07-19 02:26 UTCEPSS rescore
  65. 2026-07-18 22:59 UTCOSV refresh
  66. 2026-07-18 10:02 UTCEPSS rescore
  67. 2026-07-16 17:00 UTCEPSS rescore
  68. 2026-07-15 16:55 UTCEPSS rescore
  69. 2026-07-15 16:55 UTCEPSS rescore
  70. 2026-07-15 01:57 UTCEPSS rescore
  71. 2026-07-13 22:27 UTCEPSS rescore
  72. 2026-07-13 22:27 UTCEPSS rescore
  73. 2026-07-13 06:10 UTCEPSS rescore
  74. 2026-07-13 06:10 UTCEPSS rescore
  75. 2026-07-12 05:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-21423?
CVE-2021-21423 is a medium vulnerability published on April 6, 2021. projen is a project generation tool that synthesizes project configuration files such as package.json, tsconfig.json, .gitignore, GitHub Workflows, eslint, jest, and more, from a well-typed definition written in JavaScript. Users of projen's NodeProject project type (including any project type…
When was CVE-2021-21423 disclosed?
CVE-2021-21423 was first published on April 6, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-21423 actively exploited?
CVE-2021-21423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-21423?
CVE-2021-21423 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2021-21423?
A fix for CVE-2021-21423 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-21423

Explore →

Is Your Infrastructure Affected by CVE-2021-21423?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs