CVE-2026-41047: Lack of authentication when using the "snapshot diff" functions in qSnapper before version 1.3.3 allowed a loc

Q: How do I fix CVE-2026-41047?

qsnapper: upgrade to 1.3.3. Exact commands for each OS are on this page.

Q: Is CVE-2026-41047 being exploited?

CVE-2026-41047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-41047 affect?

CVE-2026-41047 affects qsnapper. Severity is medium (CVSS 5.5). 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.

Q: How urgent is CVE-2026-41047?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2026-41047 is a medium-severity flaw (CVSS 5.5) affecting qsnapper. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 90%)
CISA exploited list	No
Weakness	CWE-306
Published	2026-06-22
Last modified	2026-10-25

Publisher (CNA): SUSE · Vendor: presire

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-22 16:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

presire qsnapper UPGRADE

Affected: < 1.3.3

Fixed in: 1.3.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy qsnapper || rpm -q qsnapper || qsnapper --version

2. UPGRADE to 1.3.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade qsnapper

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade qsnapper

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41047?

qsnapper: upgrade to 1.3.3. Exact commands for each OS are on this page.

Is CVE-2026-41047 being exploited?

CVE-2026-41047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41047 affect?

CVE-2026-41047 affects qsnapper. Severity is medium (CVSS 5.5). 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.

How urgent is CVE-2026-41047?

Priority 22/100. No elevated risk signals yet.

Related CVEs

CVE-2026-41045 HIGH 8.1 UPGRADE A time-to-check-time-of-use in polkit authentication of qSnapper before version 1.3.3 allowed a local attacker
CVE-2026-41046 HIGH 7.3 UPGRADE A path traversal attack when using a "configName" parameter in qSnapper before version 1.3.3 allowed a local a
CVE-2026-41048 HIGH 7.1 UPGRADE Incorrect caching of authentication between different polkit methods in qSnapper before version 1.3.3 allowed
CVE-2026-41049 HIGH 7.1 UPGRADE Incorrect caching of authentication between different users of the qSnapper dbus service before version 1.3.3

References

← Back to latest CVEs