CVE-2025-1094VulnerabilityPublished 20 Feb 2025Updated 11 Oct 2026

SUSE · security update for postgresql

Affects SUSESource GCVE Database

Not known to be exploited · public exploit available (Metasploit) · 90% EPSS.

Data as of 25 Oct 2026, 19:02 UTC

Exploit forecast

Likely to be exploited

90.0% EPSS · High severity · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Metasploit module
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
Red Hatredhat/postgresql`pkg:rpm/redhat/postgresql`Other threats	Affected =9.2.24-9.el7_9.3	Fixed in–

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

AI-suggested

Red Hat has released an updated libpq package (version 12.7-1.el8_2.2) for Red Hat Enterprise Linux 8.2 AUS that addresses this vulnerability. Users should apply this official update as detailed in the Red Hat advisory (RHSA-2025:1720) and the referenced article https://access.redhat.com/articles/11258. No additional mitigation steps are indicated beyond applying the provided update.

Description

The libpq package provides the PostgreSQL client library, which allows client programs to connect to PostgreSQL servers. Security Fix(es): * postgresql: PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation (CVE-2025-1094) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerability affects the PostgreSQL client library's quoting APIs, potentially allowing malformed or maliciously crafted text inputs to bypass encoding validation and quoting neutralization. This could lead to security risks when client programs connect to PostgreSQL servers. The exact impact details and exploitation scenarios are not provided in the advisory. No known exploits in the wild have been reported.

Summary

The libpq package in Red Hat Enterprise Linux 8.2 AUS contains a vulnerability (CVE-2025-1094) where PostgreSQL quoting APIs do not properly neutralize quoting syntax in text that fails encoding validation. This could lead to security issues related to improper handling of text input in PostgreSQL client connections. Red Hat Product Security has released an update (libpq-12.7-1.el8_2.2) addressing this vulnerability. The advisory classifies the update as important and provides packages for remediation.

CWE-149Improper Neutralization of Quoting Syntax (opens in a new tab)
Variant weakness
Quotes injected into a product can be used to compromise a system. As data are parsed, an injected/absent/duplicate/malformed use of quotes may cause the process to take unexpected actions.
Developers should anticipate that quotes will be injected/removed/manipulated in the input vectors of their product. Use an appropriate combination of denylists and allowlists to ensure only valid, expected and appropriate input is processed by the system.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
While it is risky to use dynamically-generated query strings, code, or commands that mix control and data together, sometimes it may be unavoidable. Properly quote arguments and escape any special characters within those arguments.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.2.2 (opens in a new tab)
Attack patterns
Generic Cross-Browser Cross-Domain Theft (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 11:32 UTC

Public exploits and detection1 Metasploit module

WeaknessesCWE-149

Technical details

References

Community reviews

Related threats