By calling org.freedesktop.Flatpak.SystemHelper.CancelPull on another user's pull, the pull is not actually cancelled but removed from internal tracking, making it impossible for the owning user to stop it. Ongoing pulls cannot be stopped.
CVE-2026-96283
LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd 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
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 3.3
- EG Score
- 3.3LOWmedium confidence
- EG Risk
- 15EG Risk 15/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 computedSeverity33% × 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
- 3rd
- 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 27, 2026
Last Modified
September 29, 2026
References (3)
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-96283
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2539424
- secalert@redhathttps://github.com/flatpak/flatpak/security/advisories/GHSA-89xm-3m96-w3jg
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| flatpak | 1.14.10-1~deb12u1 ... 1.14.8-1~deb12u1 (10 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| flatpak | 1.16.1-1 ... 1.16.3-1~deb13u1 (7 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| flatpak | 1.16.1-1 ... 1.16.3-1~deb13u1 (7 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 16× 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.
- 2026-10-04 23:23 UTCEPSS rescore
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 21:27 UTCEG score recompute
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-29 22:12 UTCEG score recompute
- 2026-09-28 14:25 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-28 13:44 UTCEG score recompute
- 2026-09-27 22:28 UTCEG score recompute
- 2026-09-27 22:05 UTCEG score recompute▲ 3.30
- 2026-09-27 22:04 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
- 2026-09-27 21:59 UTCEG score recompute
- 2026-09-27 21:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-96283?
CVE-2026-96283 is a low vulnerability published on September 27, 2026. By calling org.freedesktop.Flatpak.SystemHelper.CancelPull on another user's pull, the pull is not actually cancelled but removed from internal tracking, making it impossible for the owning user to stop it. Ongoing pulls cannot be stopped.
When was CVE-2026-96283 disclosed?
CVE-2026-96283 was first published on September 27, 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-96283 actively exploited?
CVE-2026-96283 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-96283?
CVE-2026-96283 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96283?
No fix for CVE-2026-96283 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
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-96283
Is Your Infrastructure Affected by CVE-2026-96283?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.