VulnerabilityPublished 15 Mar 2026Updated 16 Mar 2026

CVE-2026-4190: JawherKl node-api-postgres · SQL Injection

Affects JawherKl node-api-postgresSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
JawherKlnode-api-postgres	Affected 2.0 – 2.5 6 affected builds	Fixed in–
npmnode-api-postgres`pkg:npm/node-api-postgres`Other threats	Affected 2.0 – 2.5 6 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-4190, organizations should immediately audit their use of the node-api-postgres package, specifically the User.getAll function and any usage of the 'sort' parameter. Implement strict input validation and sanitization to ensure that only expected values are accepted for sorting, ideally using a whitelist of allowed column names. Refactor SQL queries to use parameterized statements or prepared queries rather than string concatenation to prevent injection. If possible, upgrade to a patched version once available or switch to an alternative, actively maintained package with secure coding practices. Employ Web Application Firewalls (WAFs) with SQL injection detection rules to provide an additional layer of defense. Monitor logs for suspicious query patterns indicative of injection attempts. Conduct regular security assessments and code reviews focusing on database interaction layers. Finally, isolate database access with least privilege principles to limit the impact of any successful injection.

Description

CVE-2026-4190 is a medium severity SQL injection vulnerability in the JawherKl node-api-postgres package, affecting versions up to 2.5. The flaw exists in the User.getAll function within models/user.js, where the 'sort' argument is improperly sanitized, allowing remote attackers to inject malicious SQL code. Exploitation requires no authentication or user interaction and can lead to partial compromise of confidentiality, integrity, and availability of the database. Although the vendor was notified, no patch or response has been issued, and public exploit code is available. Organizations using this package in their Node.js applications are at risk of data leakage, unauthorized data manipulation, or denial of service. Mitigation involves applying input validation and sanitization on the 'sort' parameter or replacing the affected package with a secure alternative.

Impact

The SQL injection vulnerability in node-api-postgres can lead to unauthorized access to sensitive data, data corruption, or denial of service by manipulating database queries. Organizations relying on this package for backend services risk exposure of user data, intellectual property, or operational data. Attackers can exploit this flaw to extract confidential information, modify or delete records, or disrupt service availability. Given the remote and unauthenticated nature of the exploit, any publicly accessible service using the affected package is vulnerable. This can result in reputational damage, regulatory penalties due to data breaches, and operational downtime. The medium severity rating suggests that while the impact is serious, it may not lead to full system compromise without additional vulnerabilities. However, combined with other weaknesses, it could facilitate broader attacks. The absence of vendor response and patches increases the urgency for organizations to implement their own mitigations or consider alternative solutions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Mar 2026, 00:36 UTC

Technical details

References

Community reviews

Related threats