CVE-2026-107313

MEDIUMPre-NVD 4.24.2
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd 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-94546 (ENISA EUVD)Source: ENISA EUVD

4.2EG
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.1%CVSS: 4.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (PostgreSQL) states them: "Upgrade to pgjdbc 42.7.6 or later."

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.2MEDIUMmedium confidence
EG Risk
35
EG Risk 35/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)
Severity42% × 45%
Impact severity (EG Severity): CVSS 4.2 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.1%
EPSS %ILE
3rd
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 (4.2): severity, escalated by confirmed exploitation. This CVE's 4.2 is its impact severity (EG Severity), not escalated.

EG Severity
4.2 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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 (3)

Auto-updated Oct 7, 2026
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 pull request 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
GitHub advisoryMentions a patch (unverified)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava—
  • every version up to 42.7.7-1: fixed in 42.7.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libpgjava—
  • every version up to 42.7.7-1: fixed in 42.7.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 41× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-31 11:25 UTCOSV refresh
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-25 14:54 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-23 08:44 UTCEG score recompute
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-18 05:07 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 16 more
  1. 2026-10-12 16:38 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-11 20:14 UTCEG score recompute
  4. 2026-10-11 18:26 UTCEG score recompute
  5. 2026-10-11 15:00 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-09 20:20 UTCEG score recompute
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-08 20:44 UTCEG score recompute
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-07 21:25 UTCEG score recompute
  13. 2026-10-07 20:47 UTCEG score recompute
  14. 2026-10-07 19:20 UTCEG score recompute
  15. 2026-10-07 18:27 UTCEG score recomputeFirst assessed: 4.2 MEDIUM
  16. 2026-10-07 18:26 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107313?
CVE-2026-107313 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-107313 published?
The CVE record for CVE-2026-107313 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-107313 actively exploited?
CVE-2026-107313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
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).
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. Fixed versions, as the CVE record's CNA (PostgreSQL) states them: "Upgrade to pgjdbc 42.7.6 or later."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs