OSSeva Blog
ComplianceTomcat 9 after end of life in a PCI DSS 4.0 audit: what the assessor asks for
Does PCI DSS allow Tomcat 9 after 31 March 2027?
Yes, with conditions: PCI DSS v4.0.1 does not ban an end-of-life Tomcat, but it asks for an inventory, patches for critical vulnerabilities within one month of release, and a management-approved plan for outdated technology. Apache ends support for Tomcat 9.0.x on 31 March 2027 (Tomcat 9 EOL). Tomcat is often the application tier inside the cardholder data environment, so a finding there is likely to be read closely. The wording of 6.3.3 differs between v4.0 and v4.0.1 and is taken here from OSSeva's PCI DSS and end-of-life software guide; confirm it against the standard with your assessor. Tomcat extended support is the patch source for 9.0 servers that stay put.
Running Apache Tomcat in production? OSSeva patches and supports it, end-of-life versions included.
Apache Tomcat extended support: what is coveredWhich PCI DSS requirements apply to an ended Tomcat line?
Four: 6.3.1 ranks the vulnerabilities, 6.3.2 inventories the components, 6.3.3 sets the patch clock, and 12.3.4 asks for the yearly technology review and plan. The table puts a Tomcat answer next to each.
| Requirement | What it asks | What the assessor sees for Tomcat |
|---|---|---|
| 6.3.1 Vulnerability ranking | Identify new vulnerabilities from industry sources and rank them | Your ranking of each Tomcat CVE. Apache's own ratings (Important, Moderate, Low) are an input, not your ranking. |
| 6.3.2 Inventory | List bespoke and third-party software components | Every Tomcat server and every embedded copy, with version. See finding embedded Tomcat. |
| 6.3.3 Patching | Patches for critical vulnerabilities installed within one month of release | A patched build per CVE with a release date, and your install date |
| 12.3.4 Technology review | Review technologies yearly, including end-of-life announcements, with a plan approved by senior management | The 31 March 2027 date in the review, the plan, the owner and the approval |
How does the one-month patch clock work on Tomcat 9.0 after the end date?
It starts when a patched build is released, so on an ended line it starts only if someone ships a build. Apache says releases from 9.0.x after 31 March 2027 are highly unlikely and that it will not check security reports against 9.0.x. Before that date the cadence is real: Apache's security page lists 58 advisory entries fixed across ten 9.0.x releases from 7 December 2025 to 12 October 2026, 12 of them rated Important and none Critical (counted on 17 November 2026).
| State of the 9.0 server after 31 March 2027 | What the clock does |
|---|---|
| Moved to Apache's 9.1.x branch | Apache keeps releasing; the clock starts at each 9.1.x release |
| Moved to Tomcat 10.1 or 11 | Same, after the jakarta change |
| Staying on 9.0 with a provider that backports | The clock starts at the provider's build release date, which is why that date has to be on the record |
| Staying on 9.0 with no patch source | No release happens, so 6.3.3 cannot be met as written; only a documented plan and compensating measures remain |
What evidence does a patched Tomcat 9.0 build give the assessor?
A record per release, not a statement that the server is patched. For a patched build OSSeva supplies the items below, as listed in its PCI DSS guide. What stays with you is ranking the vulnerabilities, installing the build, the yearly review, the plan and the management approval.
| Evidence | What it records | Supports |
|---|---|---|
| Signed build | Release date and build identifier; GPG for packages, cosign for container images, SHA-256 checksum; patches applied to upstream source, no fork | 6.3.3 |
| CVE record and attestation letter | CVE id, CVSS, affected versions, delivery date and build identifier per release | 6.3.3, 12.3.4 |
| SBOM | The components in the build | 6.3.2 as an input |
| VEX statement per CVE | Whether the CVE is fixed in the build or does not affect it, with the reason | 6.3.3, scanner findings |
For the timing, take a Critical CVE disclosed on day 0 for a line the project no longer patches. A patched build released by day 2, within OSSeva's 48-hour Critical commitment, leaves most of the month for testing and installing. This is arithmetic, not a customer story. Extended support is a patch source that feeds the evidence; it is not a compensating control, and the guide explains why.
Which route should a cardholder-data Tomcat take?
Move to a supported line if you can; otherwise keep a patch source and a dated plan.
| Route | Fits when | Audit position |
|---|---|---|
| Apache 9.1.x | NIO connectors, no APR/native dependency | Supported branch; patches continue from Apache |
| Tomcat 10.1 or 11 | Application passes the javax to jakarta change (migration steps) | Supported branch; strongest position |
| Patched 9.0 builds | The application cannot move by 31 March 2027 | Patch source plus the CVE record; the plan in 12.3.4 shows the exit date. See Tomcat extended support |
| Nothing | Never for an internet-facing component in scope | A finding |
The checklist for the whole estate is the Tomcat 9 end of life checklist, and the longer framework view is PCI DSS and end-of-life open source software.
Sources
PCI DSS requirement wording as taken from OSSeva's PCI DSS guide (PCI SSC SAQ D documents, v4.0 and v4.0.1, read 26 October 2026; the standard itself sits behind a PCI SSC download agreement). Tomcat dates from tomcat.apache.org (end of support announcement of 11 February 2026 and the Which Version page) and CVE counts from tomcat.apache.org/security-9.html, all read on 17 November 2026. This is not legal or assessor advice; your Qualified Security Assessor decides what is acceptable in your assessment.
Frequently asked questions
Is Tomcat 9 non-compliant with PCI DSS after end of life?
Not automatically. PCI DSS v4.0.1 asks for patches for critical vulnerabilities within one month of release and a plan for outdated technology. An ended Tomcat line with no patch source fails the first; one with a patch source and a dated plan can pass both.
When does Tomcat 9 reach end of life?
Apache ends support for Tomcat 9.0.x on 31 March 2027, with a 9.1.x branch continuing to 31 December 2030 in its announcement.
Which PCI DSS requirement covers end-of-life software?
Requirement 12.3.4 asks for a yearly review of technologies, including vendor end-of-life announcements, with a plan approved by senior management. Requirement 6.3.3 covers the patching clock.
What does a QSA ask for on an end-of-life Tomcat?
The inventory entry, the ranked CVEs, the build and install records for each critical patch, and the approved plan with the end-of-life date. Tomcat extended support supplies the build and CVE records.
Tags
Related articles
Node.js 18 and 20 in PCI DSS and SOC 2 Audits: What Assessors Ask
November 17, 2026OperationsTomcat extended support: 10 questions to ask before you sign
November 17, 2026OperationsTomcat 9 end of life checklist: what to do before 31 March 2027
November 14, 2026SecurityApache Tomcat CVEs by Release: Which 9.0, 10.1 and 11.0 Version Fixes Each 2025 and 2026 CVE
October 5, 2026OperationsTomcat 9.1: Release Date, and When Tomcat 9.0 Ends (31 March 2027)
September 28, 2026ComplianceHow to Document End-of-Life Software Risk: Risk Acceptance Template for SOC 2 and PCI DSS
October 7, 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?