CVE-2026-85055

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 63% of all CVEs by exploit prediction. 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: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.22.0, field-level read permission is enforced on selected output fields but not on GraphQL or REST filter predicates. A workspace member or API key with permission to read an object but not a particular field can reference that denied field in direct filters, relation filters, or persisted view filters. The resulting totalCount and row presence reveal whether guesses match the real column, forming a boolean/count oracle that can reconstruct denied field values for records exposed by the principal's row-level policy. This issue is fixed in version 2.22.0.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 23, 2026

Advisory Details (3)

Auto-updated Sep 22, 2026
Patch available. Sources: github_pr, github_commit, github.
github_commit

commit a5108d512f75 (twentyhq/twenty)

Fix landed in twentyhq/twenty commit a5108d512f75 — awaiting tagged release

https://github.com/twentyhq/twenty/commit/a5108d512f754a937860bda5e0c2c40c7266e19e
github_pr

Block filters on restricted fields

Fix merged in twentyhq/twenty PR #22873 on 2026-07-16 — awaiting tagged release

https://github.com/twentyhq/twenty/pull/22873
github Patch Available

Field-level read bypass via filter predicate (boolean/count oracle) · Advisory · twentyhq/twenty · GitHub

Affected: 2.22.0, which enforces field read permission on the filter path

https://github.com/twentyhq/twenty/security/advisories/GHSA-v93q-4jcx-7p9m

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-09-23 20:24 UTCEG score recompute
  2. 2026-09-23 19:30 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 16:19 UTCEG score recompute
  5. 2026-09-22 15:30 UTCEG score recompute
  6. 2026-09-22 15:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85055?
CVE-2026-85055 is a high vulnerability published on September 22, 2026. Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.22.0, field-level read permission is enforced on selected output fields but not on GraphQL or REST filter predicates. A workspace member or API key with permission to read an object but not a particular field can…
When was CVE-2026-85055 disclosed?
CVE-2026-85055 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85055 actively exploited?
CVE-2026-85055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.4% of all scored CVEs.
What is the CVSS score of CVE-2026-85055?
CVE-2026-85055 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-85055?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85055, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85055?

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

Book a Demo →Browse All CVEs