OSSeva Blog
ComplianceNode.js 18 and 20 in PCI DSS and SOC 2 Audits: What Assessors Ask
What do PCI DSS and SOC 2 assessors ask about Node.js 18 and 20?
They ask whether you can show a patch source or a dated plan for a runtime the project no longer patches. Neither standard bans an end-of-life runtime. Node.js 18 ended on 30 April 2025 and Node.js 20 on 30 April 2026, so both are in scope the day an assessment starts. The questions below follow the requirement text, not a survey of assessors, so confirm them with yours. For the patched runtimes, see Node.js extended support.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredThe questions the requirements lead to
Each requirement turns into a question about records. The PCI wording is from PCI DSS v4.0.1 as quoted in our PCI DSS and end-of-life software guide; SOC 2 CC7.1 is as in our SOC 2 and end-of-life software post.
| Requirement | Question it leads to | Evidence for Node.js |
|---|---|---|
| PCI 6.3.2 inventory | Which Node.js version does each in-scope service run, including inside images? | A runtime inventory with image tags and the bundled Node.js version |
| PCI 6.3.1 ranking | How do you rank new Node.js vulnerabilities? | A ranking record per CVE, not only a scanner score |
| PCI 6.3.3 patching | Were patches for critical vulnerabilities installed within one month of release? | For an ended line, a supplier's fix record: CVE identifier, CVSS score, affected versions, delivery date and build identifier |
| PCI 12.3.4 technology review | Did you review this technology in the last 12 months, and who approved the plan for outdated technology? | A dated review, the end-of-life date and a management-approved upgrade plan |
| SOC 2 CC7.1 | Can you show production components receive security fixes? | Patch records per release, or an approved exception with compensating controls |
Why a scanner report is not enough on an ended line
The Node.js project treats ended lines as always affected, so a scanner can flag CVEs that have no fixed version for your line. Each Node.js security announcement says so, and 4 security releases have shipped since Node.js 20 ended and 8 since Node.js 18 ended, none with a build for them. An assessor reading the report sees open findings. You need either a patched build with a record per fix, or an exception that explains the compensating controls, and the upgrade date.
What answers the finding?
A patch source, an upgrade, or a documented exception with a plan.
- Upgrade to Node.js 24 or 26 where nothing blocks you: the inventory and test records are the evidence.
- Patched builds for blocked services. OSSeva's Assure tier includes a SOC 2 and PCI DSS attestation package, and the Patch tier fixes Critical CVEs within 48 hours and High within 7 days.
- Exception for an internal service due for retirement, with the date and the controls written down.
Whichever you pick, a third-party patch is not a compensating control by itself, so agree the treatment with your assessor before the assessment. Providers differ on evidence: 12 questions to ask a Node.js extended support vendor covers SBOM, VEX and CVE records.
Frequently asked questions
Is Node.js 18 allowed under PCI DSS?
PCI DSS v4.0.1 does not name Node.js versions. It asks for patches for critical vulnerabilities within one month of release (6.3.3) and a yearly technology review with a management-approved plan for outdated technology (12.3.4).
Will an unsupported Node.js version fail a SOC 2 audit?
Not automatically. CC7.1 looks for evidence that production components receive security fixes, so an ended line needs a patch source or an approved exception.
What evidence should I keep?
A runtime inventory, the end-of-life date, a fix record per CVE, the upgrade plan and who approved it.
Do I need to upgrade before the audit?
Not always. A dated plan and a patch source can satisfy the question, but confirm with your assessor.
How this was checked
PCI DSS clause wording is as recorded on this site's PCI guide, which read the PCI SSC SAQ D (v4.0.1) on 26 October 2026; the standard itself sits behind a download agreement and was not re-read today. Node.js dates and the missed-release counts are from the release schedule, endoflife.date and our Node.js vulnerabilities by version tally, checked 17 November 2026. This is not legal or assessor advice.
Tags
Related articles
Tomcat 9 after end of life in a PCI DSS 4.0 audit: what the assessor asks for
November 17, 2026ComplianceHow to Document End-of-Life Software Risk: Risk Acceptance Template for SOC 2 and PCI DSS
October 7, 2026ComplianceEnd-of-Life Software Policy Template for Open Source Infrastructure
October 7, 2026ComplianceOpen Source Compliance: 9 Audit-Ready Evidence Checks
October 6, 2026ComplianceOpen Source Compliance vs Security: What Teams Need
October 6, 2026ComplianceTools for Tracking End-of-Life Software Across an Organization
October 6, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?