Vulnerability · AZL-100014
CVE-2026-87612 affecting package nodejs 24.21.0-1
Published Sep 9, 2026 · catalog updated Oct 18, 2026 · affecting package nodejs 24.21.0-1
Open the advisory
Exploitation likelihood is not on this record for AZL-100014. A missing EPSS score is not a low risk. Compare affecting package nodejs 24.21.0-1 with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (affecting package nodejs 24.21.0-1).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- Azure Linux:3 nodejs
Type confusion in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Azure Linux:3 nodejs0 → 24.21.0-1
How to fix AZL-100014
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for AZL-100014. A missing EPSS score is not a low risk. Compare affecting package nodejs 24.21.0-1 with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 24.21.0-1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Sep 9, 2026 · OpenSSF OSV / OSV Scanner
Detected
Type confusion in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Oct 18, 2026 · OpenSSF OSV / OSV Scanner
Fix available
nodejs fixed in 24.21.0-1
Oct 18, 2026 · OpenSSF OSV / OSV Scanner
Updated
Type confusion in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryAZL-100014
CVE-2026-87612 affecting package nodejs 24.21.0-1
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.