Initiatives for
As the national authority for Cybersecurity the CCB has developed several initiatives for specific publics which are presented here.
Reference:
Advisory #2025-24
Version:
1.0
Affected software:
Node.js: v17.x, v19.x, v21.x
Type:
Insufficient security control, code execution, inadequate access control
CVE/CVSS:
• CVE-2025-23087: CVSS 8.8 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
• CVE-2025-23088: CVSS 8.8 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
• CVE-2025-23089: CVSS 8.8 (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
NodeJS: https://nodejs.org/en/blog/vulnerability/january-2025-security-releases
By exploiting these vulnerabilities, a threat actor can:
These vulnerabilities have a significant impact on confidentiality, integrity, and availability.
There is currently no evidence of these vulnerabilities being actively exploited, nor are there any proof-of-concept exploits available at this time.
These vulnerabilities allow potential exposure to unaddressed software vulnerabilities via the continued use of End-of-Life (EOL) versions that no longer receive security updates or patches.
Apart from the critical vulnerabilities, there are three vulnerabilities of lower severity:
Patch
The Centre for Cybersecurity Belgium strongly recommends installing updates for vulnerable devices with the highest priority, after thorough testing.
Monitor/Detect
The CCB recommends organizations upscale monitoring and detection capabilities to identify any related suspicious activity, ensuring a swift response in case of an intrusion.
In case of an intrusion, you can report an incident via: https://ccb.belgium.be/cert/report-incident.
While patching appliances or software to the newest version may provide safety from future exploitation, it does not remediate historic compromise.
Cyble: https://cyble.com/blog/critical-vulnerabilities-in-node-js-expose-systems/