CVE-2026-41045

HIGHNVD 7.08.1▲
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

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

A time-to-check-time-of-use in polkit authentication of qSnapper before version 1.3.3 allowed a local attacker to bypass qSnappers authentication mechanism and operate e.g. as root user.

CVSS v3
7.0
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
3.4%
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-polkit-bypass
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

1261795 – (CVE-2026-41045) AUDIT-FIND: CVE-2026-41045: qsnapper: weak Polkit authentication check

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41045?
CVE-2026-41045 is a high vulnerability published on June 22, 2026. A time-to-check-time-of-use in polkit authentication of qSnapper before version 1.3.3 allowed a local attacker to bypass qSnappers authentication mechanism and operate e.g. as root user.
When was CVE-2026-41045 disclosed?
CVE-2026-41045 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-41045 actively exploited?
CVE-2026-41045 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41045?
CVE-2026-41045 has a CVSS v3 base score of 7.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2026-41045?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41045, 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-41045

Explore →

Is Your Infrastructure Affected by CVE-2026-41045?

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

Start Free Scan →Browse All CVEs