CVE-2026-41047

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-22. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

Lack of authentication when using the "snapshot diff" functions in qSnapper before version 1.3.3 allowed a local attacker to see otherwise read protected information.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 22, 2026

Last Modified

July 7, 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-info-leak
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

1261890 – (CVE-2026-41047) AUDIT-FIND: CVE-2026-41047: qsnapper: potential information leak via "diff" methods

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41047?
CVE-2026-41047 is a medium vulnerability published on June 22, 2026. Lack of authentication when using the "snapshot diff" functions in qSnapper before version 1.3.3 allowed a local attacker to see otherwise read protected information.
When was CVE-2026-41047 disclosed?
CVE-2026-41047 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41047 actively exploited?
CVE-2026-41047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-41047?
CVE-2026-41047 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-41047?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41047, 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-41047

Explore →

Is Your Infrastructure Affected by CVE-2026-41047?

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

Start Free Scan →Browse All CVEs