Skip to content

Document OpenJS CNA reservation and publication steps - #67084

Draft
UlisesGascon wants to merge 1 commit into
nodejs:mainfrom
UlisesGascon:doc/openjs-cna-publication
Draft

UlisesGascon wants to merge 1 commit into
nodejs:mainfrom
UlisesGascon:doc/openjs-cna-publication

Conversation

@UlisesGascon

Copy link
Copy Markdown
Member

When cve_source is set to openjs-cna in .ncurc, git node security --request-cve reserves CVE ids through the OpenJS Foundation CNA instead of HackerOne. Publication to MITRE is then handled by the Publish CVEs workflow in the nodejs-private/security-release repository, which runs when the security release pull request is merged and holds until every patched version is on nodejs.org/dist.

Update the security release runbook accordingly:

  • Note the OpenJS CNA option under 'Requesting CVEs', including the resume behaviour on supervised buckets.
  • Mark 'Request publication of H1 CVE requests' in cleanup as a no-op under the OpenJS CNA path.
  • Add a Post-Release step describing the automatic publication, the nodejs.org gate, the failure issue and the delay before cve.org.
  • Scope the HackerOne form under 'Updating CVEs' to HackerOne-issued ids and point OpenJS-issued ids at the CNA coordinators.

Refs: openjs-foundation/security-wg#337
Refs: nodejs/node-core-utils#1232
Refs: https://github.com/nodejs-private/security-release/pull/87
Assisted-by: Claude

When `cve_source` is set to `openjs-cna` in `.ncurc`, `git node security
--request-cve` reserves CVE ids through the OpenJS Foundation CNA instead
of HackerOne. Publication to MITRE is then handled by the `Publish CVEs`
workflow in the nodejs-private/security-release repository, which runs
when the security release pull request is merged and holds until every
patched version is on nodejs.org/dist.

Update the security release runbook accordingly:

  * Note the OpenJS CNA option under 'Requesting CVEs', including the
    resume behaviour on supervised buckets.
  * Mark 'Request publication of H1 CVE requests' in cleanup as a no-op
    under the OpenJS CNA path.
  * Add a Post-Release step describing the automatic publication, the
    nodejs.org gate, the failure issue and the delay before cve.org.
  * Scope the HackerOne form under 'Updating CVEs' to HackerOne-issued
    ids and point OpenJS-issued ids at the CNA coordinators.

Refs: openjs-foundation/security-wg#337
Refs: nodejs/node-core-utils#1232
Refs: nodejs-private/security-release#87
Assisted-by: Claude
Signed-off-by: Ulises Gascon <ulisesgascongonzalez@gmail.com>
@UlisesGascon UlisesGascon self-assigned this Oct 28, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/security-stewards
  • @nodejs/tsc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to Node.js documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants