CVE-2026-107313

MEDIUMPre-NVD 4.24.2
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 and 42.7.5 can send the previous contents of the GSS send buffer in place of the first part of a value on a connection with GSS encryption (gssEncMode=prefer or require), and the server stores the value without an error. The buffer is 16320 bytes with MIT Kerberos. The stored value then holds bytes of the messages the driver sent just before it on the same connection, such as the statement's SQL text, its other parameters, and earlier rows of the same batch, instead of the bytes the application supplied. Values at least as long as the buffer are affected when the driver writes them from a byte array: bind parameters set with setString, setBytes, or a ByteStreamWriter, CopyIn.writeToCopy, and LargeObject.write. Most such writes fail with an ArrayIndexOutOfBoundsException instead. The default, gssEncMode=allow, does not start GSS encryption, and connections without GSS encryption are not affected. Versions 42.7.3 and earlier are not affected, and 42.7.6 fixes the problem.

CVSS v3
4.2
EG Score
4.2MEDIUMlow confidence
EG Risk
23
EG Risk 23/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity42% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 7, 2026

Last Modified

October 7, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
github_commit Patch Available

commit 96f6862bb6bc (pgjdbc/pgjdbc)

Patch available: pgjdbc/pgjdbc REL42.7.6 (contains commit 96f6862bb6bc)

https://github.com/pgjdbc/pgjdbc/commit/96f6862bb6bcadde7620688c7bce73f2d01a7ebb
github_pr Patch Available

fix: ArrayIndexOutOfBounds when write big object into GSS enabled connection, make GSSInputStream robust in face of streams that produce incomplete reads

Patch available: pgjdbc/pgjdbc REL42.7.6 (PR #3500 merged 2025-01-28)

https://github.com/pgjdbc/pgjdbc/pull/3500
githubMentions a patch (unverified)🟡 PoC Available

Driver stores bytes of earlier messages in place of a large value on GSS-encrypted connections · Advisory · pgjdbc/pgjdbc · GitHub

https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-hggc-j2qh-988m

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-07 19:20 UTCEG score recompute
  2. 2026-10-07 18:27 UTCEG score recompute
  3. 2026-10-07 18:26 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-107313?
CVE-2026-107313 is a medium vulnerability published on October 7, 2026. pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 and 42.7.5 can send the previous contents of the GSS send buffer in place of the first part of a value on a connection with GSS encryption (gssEncMode=prefer or require), and the server stores the value without an error. The buffer is 16320 bytes…
When was CVE-2026-107313 disclosed?
CVE-2026-107313 was first published on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-107313?
CVE-2026-107313 has a CVSS base score of 4.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-107313?
A fix for CVE-2026-107313 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-107313

Explore →

Is Your Infrastructure Affected by CVE-2026-107313?

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