Action required: Restage applications to address critical vulnerabilties in Java, Nginx, Node.js, Staticfile, and PHP buildpacks - UPDATE
Buildpack updates
New buildpacks have been released on Cloud.gov to address critical vulnerabilities for Java, Nginx, Node.js, and PHP. You must restage your applications to use secure versions of these buildpacks.
| Buildpack | Old Version | Updated Version | Changes |
|---|---|---|---|
| java_buildpack | v5.1.1 | v5.1.4 | Fix for CVE-2026-114938 |
| nodejs_buildpack | v1.9.7 | v1.9.8 | Remove vulnerable Node.js runtimes 22.23.4 and 24.22.2, Remove vulnerable Node.js 26.13.0 (November 2026 security release) |
| nginx_buildpack | v1.2.41 | v1.2.42 | Bump to nginx 1.30.7, 1.31.9, openresty 1.29.2.5 |
| staticfile_buildpack | v1.6.40 | v1.6.42 | Security: nginx 1.30.7 and 1.31.9 fix CVE-2026-123007 (HTTP/2 flow-control integer underflow, Critical RCE) and CVE-2026-123633 (HTTP/2 use-after-free) |
| php_buildpack | v5.1.5 | v5.1.6 | Fixes for 17 CVEs including CVE-2026-115560 (session serializer mismatch RCE) and 3 further RCEs (CVE-2026-129474, CVE-2026-129496, CVE-2026-126714); nginx CVE-2026-123007 (HTTP/2 flow-control integer underflow, CVSS v4.0 9.2 Critical, RCE) and CVE-2026-123633 (HTTP/2 use-after-free) |
What you need to do
For customers using Java, Nginx, Node.js, Staticfile, and PHP buildpacks for their applications, you will need to push or restage your application. The command to restage your application is:
cf restage <app-name> --strategy rolling
After restaging or pushing your application, to verify you are using the newest
buildpack, run cf app your-app-name and you should see one of the updated versions
listed.
Customers using a custom container image for their applications should also ensure that they are using versions of Java, Nginx, Node.js, and PHP that contain the latest security patches.
If you experience any issues after the upgrade, please reach out to support@cloud.gov.