How severe is GHSA-727h-hrw8-jg8q?

No CVSS score has been assigned to GHSA-727h-hrw8-jg8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-727h-hrw8-jg8q?

GHSA-727h-hrw8-jg8q affects the following packages: org.postgresql:postgresql (Maven). Ecosystems affected: Maven.

How do I fix GHSA-727h-hrw8-jg8q?

Update org.postgresql:postgresql to 42.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-727h-hrw8-jg8q is resolved across your whole dependency graph.

How do I detect GHSA-727h-hrw8-jg8q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.postgresql:postgresql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-727h-hrw8-jg8q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-727h-hrw8-jg8q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-727h-hrw8-jg8q can be triaged on real exposure rather than presence alone.

Is GHSA-727h-hrw8-jg8q actively exploited in the wild?

No public exploit code has been indexed for GHSA-727h-hrw8-jg8q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-727h-hrw8-jg8q?

GHSA-727h-hrw8-jg8q has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-727h-hrw8-jg8q published, and has it been updated?

GHSA-727h-hrw8-jg8q was published on March 11, 2022 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-727h-hrw8-jg8q: postgresql

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.postgresql:postgresql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary files through the loggerFile and loggerLevel connection properties. An example situation is that an attacker could create an executable JSP file under a Tomcat web root. NOTE: the vendor's position is that there is no pgjdbc vulnerability; instead, it is a vulnerability for any application to use the pgjdbc driver with untrusted connection properties.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.postgresql:postgresql`	≥ 42.1.0&&< 42.3.3	42.3.3`org.postgresql:postgresql:42.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.postgresql:postgresql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.postgresql:postgresql to 42.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-727h-hrw8-jg8q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-727h-hrw8-jg8q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-727h-hrw8-jg8q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat informs that although there's a difference from NVD CVSSv3 score there's a especial occasion in this CVE that maintain it as a moderate. The scenario for an attacker to get a benefit in this situation requires them to have access to modify a configuration file and write a file where it's needed. This require…

Product	Fixed in	Advisory
Red Hat Fuse 7.11	`jdbc-postgresql`	RHSA-2022:5532
RHINT Service Registry 2.3.0 GA	`jdbc-postgresql`	RHSA-2022:6835
RHPAM 7.13.1 async	`jdbc-postgresql`	RHSA-2022:6813

Frequently Asked Questions

In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary files through the loggerFile and loggerLevel connection properties. An example situation is that an attacker could create an executable JSP file under a Tomcat web root. NOTE: the vendor's position is that there is no pgjdbc vulnerability; instead, it is a vulnerability for any application to use the pgjdbc driver with untrusted connection properties.

O3 Security · Impact-Aware SCA

Is GHSA-727h-hrw8-jg8q in your dependencies?

O3 Security finds GHSA-727h-hrw8-jg8q across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-727h-hrw8-jg8q — postgresql