Runtime Security Guides: PHP, Node.js, GitLab and JVM Trust4
Follow each product’s advisory and the runtime actually serving the workload. Local examples compare declared versions and collect runtime evidence; they do not discover services, reproduce exploits or certify patch status.
PHP engine and web workers
Separate the PHP engine fixes, vendor backports, session follow-up and Windows package rebuild.
- PHP2Shell Response: Verify the Patched PHP Build and Web Workers
Distinguish PHP2Shell upstream fixes from vendor backports and verify the PHP workers serving requests. Track the session follow-up and Windows Brotli rebuild separately.
Brotli paths and Node.js rollout
Trace untrusted decompression and connect runtime fix evidence to every worker and replica.
- Node2Shell Response: Trace Brotli Decompression and Verify Node.js Rollout
Check CVE-2026-111497 fixes, Brotli input paths and misleading version labels. Collect runtime evidence and distinguish installation from adoption by every worker and replica.
GitLab server upgrade
Compare the RCE release threshold and follow upgrade stops before verifying adoption.
- GitLab2Shell Response: CVE-2026-110264 Version Checks and Upgrade Paths
Separate the GitLab regular-expression RCE’s first fixed releases from verified deployment. Use an offline version comparator and follow required upgrade stops and migrations.
JVM certificate trust
Distinguish supplier distrust guidance from the CA inventory of a newly started JVM.
- JDK eMudhra Certificates: Inspect the Running JVM and Its Trust Store
Distinguish Oracle, Temurin and Ubuntu eMudhra distrust guidance. Inspect JSSE trust-store selection and certificate fingerprints without treating version labels or aliases as a verdict.