CVE-2026-41048

HIGHNVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-22. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Incorrect caching of authentication between different polkit methods in qSnapper before version 1.3.3 allowed a local attacker to use functions like "restore from snapshot" even if only allowed to do "delete snapshot".

CVSS v3
7.1
EG Score
7.1(high)
EPSS
3.2%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 28, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_release.
generic

qSnapper: Various Security Issues in Privileged D-Bus Service (CVE-2026-41045 through CVE-2026-41048) | SUSE Security Team Blog

https://security.opensuse.org/2026/05/26/qsnapper-dbus-issues.html#issue-auth-caching
github_release Patch Available

qSnapper 1.3.3

Patch available: presire/qSnapper v1.3.3

https://github.com/presire/qSnapper/releases/tag/v1.3.3
generic

1262218 – (CVE-2026-41048, CVE-2026-41049) AUDIT-FIND: CVE-2026-41048,CVE-2026-41049: qsnapper: authentication bypass across clients via shared `m_authenticated` flag

https://bugzilla.suse.com/show_bug.cgi?id=1262218

Vendor Advisories for CVE-2026-41048(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 70× 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-07-06 22:56 UTCEG score recompute
  2. 2026-07-06 22:56 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:50 UTCEG score recompute
  6. 2026-07-06 09:50 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:37 UTCEG score recompute
  10. 2026-07-05 20:37 UTCGHSA enrichment
  11. 2026-07-05 07:30 UTCEG score recompute
  12. 2026-07-05 07:30 UTCGHSA enrichment
  13. 2026-07-04 18:24 UTCEG score recompute
  14. 2026-07-04 18:24 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 05:12 UTCEG score recompute
  17. 2026-07-04 05:12 UTCGHSA enrichment
  18. 2026-07-03 16:04 UTCEG score recompute
  19. 2026-07-03 16:04 UTCGHSA enrichment
  20. 2026-07-03 02:58 UTCEG score recompute
  21. 2026-07-03 02:58 UTCGHSA enrichment
  22. 2026-07-02 13:52 UTCEG score recompute
  23. 2026-07-02 13:52 UTCGHSA enrichment
  24. 2026-07-02 00:46 UTCEG score recompute
  25. 2026-07-02 00:46 UTCGHSA enrichment
Show 45 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-07-01 11:34 UTCEG score recompute
  3. 2026-07-01 11:34 UTCGHSA enrichment
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 22:28 UTCEG score recompute
  6. 2026-06-30 22:28 UTCGHSA enrichment
  7. 2026-06-30 09:22 UTCEG score recompute
  8. 2026-06-30 09:22 UTCGHSA enrichment
  9. 2026-06-29 20:16 UTCEG score recompute
  10. 2026-06-29 20:16 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 07:10 UTCEG score recompute
  13. 2026-06-29 07:10 UTCGHSA enrichment
  14. 2026-06-28 18:00 UTCEG score recompute
  15. 2026-06-28 18:00 UTCGHSA enrichment
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEG score recompute 1.30
  19. 2026-06-28 04:54 UTCGHSA enrichment
  20. 2026-06-28 01:44 UTCNVD updateCVSS v3 → 7.1
  21. 2026-06-27 15:48 UTCEG score recompute
  22. 2026-06-27 15:48 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-27 02:42 UTCEG score recompute
  25. 2026-06-27 02:41 UTCGHSA enrichment
  26. 2026-06-26 13:35 UTCEG score recompute
  27. 2026-06-26 13:35 UTCGHSA enrichment
  28. 2026-06-26 00:28 UTCEG score recompute
  29. 2026-06-26 00:28 UTCGHSA enrichment
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 11:20 UTCEG score recompute
  33. 2026-06-25 11:20 UTCGHSA enrichment
  34. 2026-06-24 22:14 UTCEG score recompute
  35. 2026-06-24 22:14 UTCGHSA enrichment
  36. 2026-06-24 14:05 UTCEPSS rescore
  37. 2026-06-24 09:08 UTCEG score recompute
  38. 2026-06-24 09:08 UTCGHSA enrichment
  39. 2026-06-23 21:33 UTCEPSS rescore
  40. 2026-06-23 20:02 UTCEG score recompute
  41. 2026-06-23 20:02 UTCGHSA enrichment
  42. 2026-06-23 06:55 UTCEG score recompute
  43. 2026-06-23 06:55 UTCGHSA enrichment
  44. 2026-06-22 17:47 UTCEG score recompute
  45. 2026-06-22 17:45 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-41048?
CVE-2026-41048 is a high vulnerability published on June 22, 2026. Incorrect caching of authentication between different polkit methods in qSnapper before version 1.3.3 allowed a local attacker to use functions like "restore from snapshot" even if only allowed to do "delete snapshot".
When was CVE-2026-41048 disclosed?
CVE-2026-41048 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41048 actively exploited?
CVE-2026-41048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41048?
CVE-2026-41048 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-41048?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41048, 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-41048

Explore →

Is Your Infrastructure Affected by CVE-2026-41048?

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