InformationalVulnerabilityMonitoring

Bishop Fox reports how to trace CVE fixes in deployed Node.js and PHP code

Bishop Fox reports lab tests showing version strings can mislead on patch status; check the code actually loaded before acting.

Published
Fixed in
Node.js 24.22.1 (per its release notes, as reported by Bishop Fox); Ubuntu libapache2-mod-php8.3 8.3.6-0ubuntu0.24.04.13; libwebp 1.3.2
Exploitation
No evidence in the source. Bishop Fox describes controlled lab experiments, not attacks.

Live scores

CVE-2026-111497
EPSS
0.826
very likely to be attacked soon
VEDAS
0.976
strong exploit evidence
On CISA KEV
Yes, since 2026-10-27
Detection rule
No public rule yet
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-27CVE-2026-111497 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-27CVE-2026-111497 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 3 days before CISA confirmed attacks.

Live scores

CVE-2026-109618
EPSS
1.000
very likely to be attacked soon
VEDAS
0.983
strong exploit evidence
On CISA KEV
Yes, since 2026-10-26
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-26CVE-2026-109618 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-26CVE-2026-109618 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 5 days before CISA confirmed attacks.

Live scores

CVE-2026-109619
EPSS
1.000
very likely to be attacked soon
VEDAS
0.985
strong exploit evidence
On CISA KEV
Yes, since 2026-10-26
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-26CVE-2026-109619 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-26CVE-2026-109619 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 2 days before CISA confirmed attacks.

Live scores

CVE-2023-4863
EPSS
1.000
very likely to be attacked soon
VEDAS
0.988
strong exploit evidence
On CISA KEV
Yes, since 2023-09-13
Detection rule
No public rule yet
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1CVE-2023-4863 EPSS over time2025-042026-11-17
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.5CVE-2023-4863 VEDAS over time2025-042026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

What happened

Bishop Fox reports, in a technical research post dated Nov 17, 2026 by Emilio Gallegos, that checking the code an application actually uses helps establish whether a fix applies Bishop Fox. This is the outlet’s own lab research. It is not a vendor or CERT advisory, and no other outlet is cited here. According to Bishop Fox, the post was prompted by the PHP2Shell and Node2Shell disclosures Bishop Fox.

The post describes three experiments:

  • Node.js and Brotli. Bishop Fox says it ran the same application in official Node.js 24.22.0 and 24.22.1 images, immediately before and after the fix for CVE-2026-111497 (the identifier as written in the post). It says the built-in fetch() decoded a Brotli response in both builds even though the client sent Accept-Encoding: identity. Both builds reported Brotli 1.2.0, and the Node.js 24.22.1 release notes record the cherry-picked fix. Docker Scout 1.18.3 found no separate Brotli entry in either image’s SBOM, but it did distinguish the two Node.js releases Bishop Fox. The post says an attacker would need control over a response the application retrieves to supply malicious Brotli data through this path Bishop Fox.
  • PHP backport on Ubuntu. Bishop Fox says Ubuntu’s PHP 8.3.6 package still reported 8.3.6 in both CLI and HTTP, despite backported fixes. It says it inspected the Apache worker process and found libphp8.3.so mapped, whose package record is libapache2-mod-php8.3 8.3.6-0ubuntu0.24.04.13. Per the post, Ubuntu’s security notice lists that revision as fixed for CVE-2026-109618 and CVE-2026-109619. Bishop Fox says relying only on upstream’s fixed version would have flagged this patched server Bishop Fox.
  • libwebp outside the system package. Bishop Fox says it built libwebp 1.3.1 (affected) and 1.3.2 (fixed) under /opt/libwebp in two ImageMagick setups, both also keeping Ubuntu’s fixed libwebp7 package, revision 1.3.2-0.4build3. It says ldd on the convert executable showed no libwebp match, while ImageMagick’s WebP module resolved to the libraries under /opt in both setups. The post refers to CVE-2023-4863 as background Bishop Fox.

Not confirmed: the source text available to us is truncated in the libwebp section, so its remaining findings are not covered here. The sources do not state severity scores, exploitation in the wild, or full affected-version ranges for any CVE.

Am I affected?

The post does not describe a new flaw that affects a defined product list. It describes how patch status can be misjudged. According to Bishop Fox, it may be relevant if you:

  • run Node.js and rely on a Brotli version string or SBOM entry to judge the fix, since the post says the Node.js release was the relevant patch identifier for these images Bishop Fox;
  • run Ubuntu PHP packages and compare the reported PHP version against upstream fixed versions Bishop Fox;
  • have a separately installed libwebp alongside the system package, for example for ImageMagick Bishop Fox.

Whether your own systems are vulnerable to the named CVEs is not confirmed by the source.

What to do now

  1. Identify which component actually handles the request in your deployment. Bishop Fox did this for PHP by inspecting the Apache worker process and its mapped module, then checking that module’s package record Bishop Fox.
  2. Compare the full package revision, not only the upstream version, against the distribution’s security notice. The post says Ubuntu’s fixed revision was needed to recognise its backport Bishop Fox.
  3. For Node.js, map the image or build to its release notes. The post says the release was the patch identifier because the Brotli version string did not differ Bishop Fox.
  4. If a library is installed outside the system package, check which copy the relevant loadable module resolves to, since the post says ldd on the main executable showed no libwebp match Bishop Fox.
  5. Read the full post and the cited vendor notices before changing remediation priorities.

Sources