Security advisory
`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 modi
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2021-21423
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 11:33 UTC · Revision 1
Source evidence
`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 modi
osv:CVE-2021-21423
Complete source record
{
"id": "d075bdb08ac9e93987d61fa803491c07e56de31327d300b039d5df94675c1829",
"url": "https://osv.dev/vulnerability/CVE-2021-21423",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2021-21423",
"summary": "`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 modi",
"evidence": "osv:CVE-2021-21423",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2021-21423",
"aliases": [
"CVE-2021-21423",
"GHSA-gg2g-m5wc-vccq",
"PYSEC-2021-111"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/projen/projen",
"type": "GIT",
"events": [
{
"introduced": "6b60a0cec5fa4485e7da8426cfab27ce2288afaa"
},
{
"fixed": "8ecef8a424526cab7bc55ba2b6ad8c1db93756f6"
},
{
"fixed": "36030c6a4b1acd0054673322612e7c70e9446643"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:projen_project:projen:*:*:*:*:*:node.js:*:*",
"range": [
{
"introduced": "0.6.0"
},
{
"fixed": "0.16.41"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "36030c6a4b1acd0054673322612e7c70e9446643"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v0.16.40",
"v0.16.39",
"v0.16.38",
"v0.16.37",
"v0.16.36",
"v0.16.35",
"v0.16.34",
"v0.16.33",
"v0.16.32",
"v0.16.31",
"v0.16.30",
"v0.16.29",
"v0.16.28",
"v0.16.27",
"v0.16.26",
"v0.16.25",
"v0.16.24",
"v0.16.23",
"v0.16.22",
"v0.16.21",
"v0.16.20",
"v0.16.19",
"v0.16.18",
"v0.16.17",
"v0.16.16",
"v0.16.15",
"v0.16.14",
"v0.16.13",
"v0.16.12",
"v0.16.11",
"v0.16.10",
"v0.16.9",
"v0.16.8",
"v0.16.7",
"v0.16.5",
"v0.16.3",
"v0.16.2",
"v0.16.1",
"v0.16.0",
"v0.15.18",
"v0.15.17",
"v0.15.16",
"v0.15.15",
"v0.15.14",
"v0.15.13",
"v0.15.12",
"v0.15.11",
"v0.15.10",
"v0.15.9",
"v0.15.8",
"v0.15.7",
"v0.15.6",
"v0.15.5",
"v0.15.4",
"v0.15.3",
"v0.15.2",
"v0.15.1",
"v0.15.0",
"v0.14.10",
"v0.14.9",
"v0.14.8",
"v0.14.7",
"v0.14.6",
"v0.14.5",
"v0.14.4",
"v0.14.3",
"v0.14.2",
"v0.14.1",
"v0.14.0",
"v0.13.13",
"v0.13.12",
"v0.13.11",
"v0.13.10",
"v0.13.9",
"v0.13.8",
"v0.13.7",
"v0.13.6",
"v0.13.5",
"v0.13.4",
"v0.13.3",
"v0.13.2",
"v0.13.1",
"v0.13.0",
"v0.12.15",
"v0.12.14",
"v0.12.13",
"v0.12.12",
"v0.12.11",
"v0.12.10",
"v0.12.9",
"v0.12.8",
"v0.12.7",
"v0.12.6",
"v0.12.5",
"v0.12.4",
"v0.12.3",
"v0.12.2",
"v0.12.1",
"v0.12.0",
"v0.11.0",
"v0.10.1",
"v0.10.0",
"v0.9.3",
"v0.9.2",
"v0.9.1",
"v0.9.0",
"v0.8.0",
"v0.7.0",
"v0.6.22",
"v0.6.21",
"v0.6.20",
"v0.6.19",
"v0.6.18",
"v0.6.17",
"v0.6.16",
"v0.6.15",
"v0.6.14",
"v0.6.13",
"v0.6.12",
"v0.6.11",
"v0.6.10",
"v0.6.9",
"v0.6.8",
"v0.6.6",
"v0.6.5",
"v0.6.4",
"v0.6.3",
"v0.6.2",
"v0.6.1",
"v0.6.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2021-21423.json"
}
}
],
"modified": "2026-10-20T10:54:30.282855637Z",
"provider": "osv",
"references": [
"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq",
"https://www.npmjs.com/package/projen",
"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2021-21423",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 385460,
"published_at": "2021-04-06T19:15:14.787+00:00"
}