Authenticated code execution via unsanitized npm version specifier
Published Jan 1, 2026 · Updated Jan 1, 2026
Code injection in Signal K Server before 2.19.0 allows remote authenticated users to execute commands via a crafted npm version specifier. The app-store installation route passes its unvalidated version parameter into npm, which accepts attacker-controlled repositories or tarballs and runs their postinstall scripts. Administrative access is required, and successful exploitation executes code with the privileges of the Signal K Server process.
Summary
What happened
Code injection in Signal K Server before 2.19.0 allows remote authenticated users to execute commands via a crafted npm version specifier. The app-store installation route passes its unvalidated version parameter into npm, which accepts attacker-controlled repositories or tarballs and runs their postinstall scripts. Administrative access is required, and successful exploitation executes code with the privileges of the Signal K Server process.
The record
- CVE
- CVE-2025-68619
- Published
- Jan 1, 2026
- Updated
- Jan 1, 2026
- Vendor
- Signal K
- Product
- Signal K Server
- Classifications
- CWE-94, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 1, 2026CVE publishedPublication date reported by the CVE source.
- Jan 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.19.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Tarball-based malicious npm installation proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo