PHP and Node.js reports: Versions, status and risk
By Thomas Trenz, co-founder and CEO of JDisc GmbH
Security baseline checked: 22 October 2026. This article describes the reports for the security releases of 21 October 2026.
Introduction
When a runtime vulnerability becomes public, finding an application name is only the first step. You also need to know which version is present, whether discovery observed it running, and which entries require an update or further investigation.
The PHP and Node.js security releases of 21 October 2026 make that distinction particularly relevant. PHP addressed two critical remote-code-execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619. Node.js published a separate release addressing high-severity issues, including the Brotli decoder vulnerability CVE-2026-111497. See the official PHP advisory and Node.js security release for their scope and remediation guidance.
Our introductory article, PHP and Node.js vulnerabilities: Find the runtimes you need to patch, explains why installed-software lists alone can overlook runtime usage. This technical companion focuses on two custom reports in JDisc Discovery and how to interpret their findings.
Two custom reports with the same assessment pattern
The reports are named PHP – Software Status and Risk and Node.js – Software Status and Risk. Both work through the same practical questions:
- Which relevant runtime installations or core interpreter files can be identified in the discovery database?
- What version information is available for each entry?
- Does the applicable inventory evidence establish a running instance?
- What activity-based risk classification and version-related action follow?
The reports use the data collected by JDisc Discovery. They are an assessment of your inventory, rather than a continuous live view of every process. Their usefulness therefore depends on scan coverage, data freshness, and the details the target system exposes.
JDisc Discovery’s software inventory and custom reporting provide the foundation. Registered applications help locate conventional installations. Process, service, executable, and module information add evidence about runtime presence and use. A device may appear in several rows because it has different runtimes, versions, or installation locations. Review those entries individually rather than treating repeated device names as duplicates.
Why process modules matter for PHP
PHP does not have to run as a separate process named php. With Apache and mod_php, a PHP DLL or shared library is loaded inside the Apache process. Looking only at httpd or apache2 would tell you the web server exists, but not which PHP component it is using.
JDisc’s process module collection records DLLs, JARs, and shared libraries associated with processes. The PHP report can use the relevant runtime evidence to make embedded PHP visible. The broader JAR collection is useful for other software investigations; JARs are not PHP interpreters.
The reports focus on identified runtimes, launchers, and core interpreter files. Functional PHP extensions such as php5-json and unrelated package-manager entries are excluded. That keeps the result focused on runtime installations rather than turning every PHP-related package name into another interpreter finding.
Read the six report columns
Both PHP and Node.js reports use the same six-column layout. The labels below match the report interface.
| Column | What it tells you |
|---|---|
| Device Name | The device name recorded in JDisc Discovery. Several rows can identify different runtime installations on the same system. |
| Main IP | The recorded main discovery IP address. IPv6 is preferred when both IPv4 and IPv6 main addresses are available. The cell is empty if no main address is recorded. |
| Software with Version | The identified software, runtime, or core interpreter file and its recorded version. Unknown or incomplete versions remain visible. An installation path is added when needed to distinguish otherwise identical entries on the same device. |
| Status | Running when matching process, loaded runtime module, or running-service evidence is recorded. Installed when presence is established without a corresponding running observation, or when a consistent recorded stopped VM state overrides older process evidence. |
| Risk Level | High for Running, Medium for Installed. This activity-based classification is independent of the version assessment. |
| Action | Update, Clarify installed version, or an empty cell, according to the report’s version rules. |
The distinction between the last two columns is essential. Risk Level describes recorded activity. Action describes the version assessment. Neither column is a substitute for the other.
Running versus installed: What the status establishes
Running means discovery has a matching running observation in the applicable records. That can be a process, a loaded runtime module, or a running service. For PHP inside Apache, module evidence matters even when no standalone PHP executable is running.
Installed means the runtime is present in the inventory without an established running match. It is tempting to read that as “not used,” but the data supports a narrower conclusion: the applicable discovery evidence did not establish that it was running. A scheduled job could execute between scans. A stopped process could start later. Missing access could prevent collection of the relevant evidence.
Records can also come from earlier scans. Where a consistent recorded stopped VM state applies, it can override older process evidence and produce Installed. That prevents an old process observation from automatically taking precedence over that VM state. It still does not make the report a live monitor of the VM’s current state.
Check scan timing and collection success when a status looks unexpected. Use the JDisc documentation and data-quality guidance when reviewing the underlying discovery setup.
High and Medium set activity priorities
The reports classify Running as High and Installed as Medium. For an outdated runtime, this gives you a practical first sorting criterion: investigate the observed running copy first, while keeping the installed-only copy in the update plan.
This is an activity-based prioritization rule, not a CVSS score or proof that an exploit is reachable. Business criticality, network exposure, application configuration, and vendor patch evidence still belong in the final assessment.
A running instance that already meets the report’s fixed-release baseline still receives High. If its version needs no follow-up under those rules, its Action cell is empty. That is expected. Patching can resolve an Update action without changing Running or High.
Likewise, Medium does not mean “leave this version installed.” An outdated installation remains an update task even if discovery did not observe it running. It could be started later or used outside the observation window. Upgrade affected versions in both categories.
How the Action column handles versions
Update indicates that the identified version is below the applicable fixed release, or that a legacy branch requires migration to a supported, patched version. It is a version-related follow-up, not an indication that the report performed an exploit test.
Clarify installed version means the available version or build information is insufficient for an assessment. Find the actual runtime build using the system’s package information, the application vendor’s documentation, or the underlying interpreter file. Avoid checking only the system-wide runtime if the finding points to an application-specific copy.
Incomplete metadata does not always force an unknown result. If the known version components already establish that a version predates the fix, the report can show Update. If they do not establish that, clarification is required. A blank Action means the report’s version rules found no follow-up action; it does not certify the entire application as secure.
For context, the upstream fixed PHP releases were 8.2.35, 8.3.36, 8.4.27, and 8.5.12. The Node.js releases were 22.23.4, 24.22.1, and 26.12.1. Use the linked vendor advisories for these branch-specific baselines. Distribution or application vendors may backport fixes, so compare complete package revisions and vendor security notices before deciding that an older-looking build is unpatched.
Example findings: Read activity and action together
The following rows are illustrative report excerpts, not results from a customer environment. “Empty” represents a blank Action cell.
| Software with Version | Status | Risk Level | Action |
|---|---|---|---|
| PHP 8.3.35 | Running | High | Update |
| PHP 8.3.35 | Installed | Medium | Update |
| Node.js 24.22.1 | Running | High | Empty |
| Node.js, version unknown | Installed | Medium | Clarify installed version |
The two PHP rows require the same update follow-up, but the observed running copy takes the higher activity priority. The patched Node.js example retains High because it is running. The unknown Node.js version remains unresolved until its build can be verified.
When several entries belong to the same device, compare the version and any displayed installation path. Updating the registered system package may leave another application’s bundled runtime untouched. Preserve that distinction when assigning work to the system or application owner.
Work through findings and verify the result
Begin with fresh discovery data for the relevant systems. Confirm that installed-software collection and the required process, service, or module collection completed successfully. An empty result on a system that could not be scanned needs a coverage check.
Review High entries with Update or Clarify installed version first, adding your own exposure and business context. Then work through Medium entries with those actions. Verify unknown builds and vendor backports rather than silently dismissing them. Keep each installation copy attached to the right remediation task.
Apply updates through your operating-system or application maintenance process. Restart affected services or workers where required so they load the new interpreter or library. Run discovery again, reopen both reports, and check whether the relevant Action changed. A correctly updated runtime can remain Running / High; that alone does not mean the update failed.
Retain direct patch evidence alongside the report result. Discovery helps you find and reassess runtime copies, while the vendor’s package or build information establishes what was actually fixed.
Download and install the custom reports
To install them, open the custom report section in JDisc Discovery and import the downloaded .rep files. Import each report, then open PHP – Software Status and Risk and Node.js – Software Status and Risk to review the entries in your database.
Importing the report definitions does not refresh discovery data. If the inventory is old or the required collection was not enabled, run the appropriate discovery scan and then review the reports again. If you are evaluating the workflow for the first time, you can download JDisc Discovery and test the reports against representative PHP and Node.js systems.
Frequently Asked Questions
These answers clarify the status, risk, and version rules used by the PHP and Node.js reports. They also cover practical questions about missing metadata, multiple installations, and importing the report definitions.
Risk Level is based on recorded activity, independently of the version. A running runtime receives High even when the report’s version rules identify no follow-up action. Read it together with Action.
No. Installed means that the applicable inventory does not establish a matching running instance, or that a consistent recorded stopped VM state overrides older process evidence. It is not proof that the runtime is stopped now or never used.
Yes. Medium changes the activity priority, not the need to fix an affected version. Include installed-only copies in the update plan.
Verify the actual runtime build and its patch status. Use the package revision, interpreter file, installation location, and application-vendor information as appropriate. The report lacks enough version or build information to decide the next action reliably.
Different software, versions, or installation locations can produce separate entries. Review them individually so an update to one runtime copy does not obscure another copy that still needs attention.
No. It means the report’s version rules identify no follow-up action for that entry. Coverage, data freshness, other vulnerabilities, and application exposure still need their own assessment.
Download the PHP and Node.js .rep files and import them within JDisc Discovery’s custom report section. Then open both reports. Run discovery separately when you need to refresh the underlying inventory.



