CVE-2026-107315

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (10th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-94650 (ENISA EUVD)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 through 42.7.13 pads a value that is shorter than its declared length with bytes left in its send buffer instead of zeros, and the server stores those bytes as part of the value. The bytes are messages the driver sent earlier on the same connection: SQL text and parameter values of recent statements, which on a pooled connection can come from other requests. Each padded value can carry up to 8192 bytes of this traffic, or 16320 bytes on a connection with GSS encryption. The padding happens when an application declares a length larger than the data it supplies, through PreparedStatement.setObject with a ByteStreamWriter, CopyIn.writeToCopy, PGCopyOutputStream.write, LargeObject.write, or Blob.setBytes. The driver accepts these calls without an error. An attacker who can make the application store such a value and read it back can collect earlier traffic. Applications whose declared lengths always match their data are not affected. Versions 42.7.3 and earlier pad with zeros.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Driver stores bytes of earlier statements when it pads a value shorter than its declared length · Advisory · pgjdbc/pgjdbc · GitHub

https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-f64h-wr5q-3qf3

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.5.4-1 ... 42.7.9-1 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.7.10-1 ... 42.7.9-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava42.7.10-1 ... 42.7.9-1 (9 versions)
  • every version up to 42.7.14-1: fixed in 42.7.14-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-31 11:25 UTCOSV refresh
  15. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-25 14:54 UTCEchelonGraph re-scored
  22. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-23 08:44 UTCEchelonGraph re-scored
  25. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 24 more
  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-18 05:07 UTCEchelonGraph re-scored
  5. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-12 16:38 UTCEchelonGraph re-scored
  10. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-11 20:14 UTCEchelonGraph re-scored
  12. 2026-10-11 18:26 UTCEchelonGraph re-scored
  13. 2026-10-11 15:00 UTCEchelonGraph re-scored
  14. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-10 17:07 UTCEchelonGraph re-scored
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-08 21:01 UTCEchelonGraph re-scored
  19. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-08 15:24 UTCEchelonGraph re-scored
  21. 2026-10-08 14:56 UTCEchelonGraph re-scored
  22. 2026-10-08 00:30 UTCEchelonGraph re-scored
  23. 2026-10-07 23:21 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
  24. 2026-10-07 23:21 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107315?
CVE-2026-107315 is a medium-severity vulnerability; its CVE record was published on October 7, 2026. pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 through 42.7.13 pads a value that is shorter than its declared length with bytes left in its send buffer instead of zeros, and the server stores those bytes as part of the value. The bytes are messages the driver sent earlier on the same…
When was the CVE record for CVE-2026-107315 published?
The CVE record for CVE-2026-107315 was published on October 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-107315 actively exploited?
CVE-2026-107315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107315?
CVE-2026-107315 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107315?
A fix for CVE-2026-107315 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107315

Explore →

Is Your Infrastructure Affected by CVE-2026-107315?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs