Finding and attribution
The release workflow does not pin maintainer authorization to a commit, then checks out and executes code from a mutable pull-request ref with repository write-token access.
Product: mongodb/js-bson release_notes GitHub Actions workflow. AI system: GitHub Security Lab AI agent (system not named in advisory). Team / organization: GitHub Security Lab.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): GHSL’s primary AI-agent index includes this advisory in its AI-discovered list. The item advisory credits only the human researcher and provides no agent-specific role; attribution is index-level only.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The primary advisory documents the race and fix; no exploitation in the wild is claimed.
Remediation status: fix documented. Fixed in PR #929 on 2026-09-03. A maintainer authorization is required to trigger the workflow.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 16 Sep 2026. AI attribution dated 16 Sep 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: code execution.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Case-level evidence: code execution.
Prerequisites / affected scope: External pull-request author can update the ref after maintainer review; code runs with the listed write permissions..
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Fixed in PR #929 on 2026-09-03. A maintainer authorization is required to trigger the workflow.