CVE-2026-41049

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
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 users of the  qSnapper dbus service before version 1.3.3 allowed any local attacker to use dbus functions after a privileged users has authenticated for them.

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

Published

June 22, 2026

Last Modified

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

Related CVEs(same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41049?

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

Start Free Scan →Browse All CVEs