CVE-2026-97027

LOWPre-NVD 3.63.6—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). 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
3.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.6Exploit: None knownExposed services: Not assessed

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

Flatpak passes through arbitrary vendor-extension keys unmodified when exporting an application's Desktop Entry (.desktop) and D-Bus Service (.service) files, instead of validating against an allowlist. A malicious Flatpak app can use this to cause denial of service (e.g. forced application restart loops) or to influence host D-Bus/systemd activation behavior beyond what the sandbox is intended to permit.

CVSS v3
3.6
EG Score
3.6LOWmedium confidence
EG Risk
16
EG Risk 16/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
Severity36% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

September 28, 2026

Last Modified

September 29, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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-03 14:26 UTCEPSS rescore
  2. 2026-10-02 17:57 UTCEPSS rescore
  3. 2026-10-02 14:59 UTCEG score recompute
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-29 20:31 UTCEG score recompute
  7. 2026-09-29 19:44 UTCEG score recompute
  8. 2026-09-28 21:18 UTCEG score recompute
  9. 2026-09-28 21:03 UTCEG score recompute
  10. 2026-09-28 21:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97027?
CVE-2026-97027 is a low vulnerability published on September 28, 2026. Flatpak passes through arbitrary vendor-extension keys unmodified when exporting an application's Desktop Entry (.desktop) and D-Bus Service (.service) files, instead of validating against an allowlist. A malicious Flatpak app can use this to cause denial of service (e.g. forced application restart…
When was CVE-2026-97027 disclosed?
CVE-2026-97027 was first published on September 28, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97027 actively exploited?
CVE-2026-97027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97027?
CVE-2026-97027 has a CVSS base score of 3.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97027?
No fix for CVE-2026-97027 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-97027?

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