CVE-2026-105612

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (4th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-28) is not newer than that change (2026-11-12), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-112284 (ENISA EUVD) · GHSA-5wcf-v8v8-f5c4 (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.3Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

PostgreSQL Anonymizer contains a vulnerability that data-modifying CTEs to bypass the read-only restriction of masked roles. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
4th
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.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% 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 every mission impact level.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 every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (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 28, 2026

Last Modified

November 12, 2026

References (1)

Vendor Advisories for CVE-2026-105612(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 24× 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-13 16:50 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-11-12 21:08 UTCEchelonGraph re-scored▲ 0.80
  3. 2026-11-12 21:08 UTCGHSA enrichmentGHSA-5wcf-v8v8-f5c4 · GitHub severity LOW · GitHub CVSS 3.5
  4. 2026-11-12 21:07 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  5. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-11-05 17:28 UTCEchelonGraph re-scored
  13. 2026-11-05 17:28 UTCGHSA enrichmentGHSA-5wcf-v8v8-f5c4 · GitHub severity LOW · GitHub CVSS 3.5
  14. 2026-11-05 17:09 UTCEchelonGraph re-scored
  15. 2026-11-05 17:09 UTCGHSA enrichmentGHSA-5wcf-v8v8-f5c4 · GitHub severity LOW · GitHub CVSS 3.5
  16. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-29 15:46 UTCGHSA enrichmentGHSA-5wcf-v8v8-f5c4 · GitHub severity LOW · GitHub CVSS 3.5
  25. 2026-10-28 18:59 UTCEchelonGraph re-scored
Show 4 more
  1. 2026-10-28 18:59 UTCGHSA enrichmentGHSA-5wcf-v8v8-f5c4 · GitHub severity LOW · GitHub CVSS 3.5
  2. 2026-10-28 18:01 UTCENISA EUVD ID recordedEUVD-2026-112284 · Source: ENISA EUVD
  3. 2026-10-28 17:40 UTCEchelonGraph re-scoredFirst assessed: 3.5 LOW
  4. 2026-10-28 17:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-105612?
CVE-2026-105612 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. PostgreSQL Anonymizer contains a vulnerability that data-modifying CTEs to bypass the read-only restriction of masked roles. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions
When was the CVE record for CVE-2026-105612 published?
The CVE record for CVE-2026-105612 was published on October 28, 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 November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-105612 actively exploited?
CVE-2026-105612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105612?
CVE-2026-105612 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-105612?
The CVE record for CVE-2026-105612 names the fix: "The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions". The vendor advisories EchelonGraph has for CVE-2026-105612 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105612?

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

Book a Demo →Browse All CVEs