dbcve.org
SpacesnifferApplication · Uderzo

CVE-2026-26738

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer Overflow vulnerability in Uderzo Software SpaceSniffer v.2.0.5.18 allows a remote attacker to execute arbitrary code via a crafted .sns snapshot file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in SpaceSniffer v.2.0.5.18 when parsing .sns snapshot files. The application fails to properly validate the size or content of data within crafted .sns files, allowing an attacker to overwrite adjacent memory and achieve arbitrary code execution through a malicious file.

MitigationUntil an official vendor patch is released, restrict usage of SpaceSniffer to only trusted .sns files from known sources. Consider implementing file type restrictions or application whitelisting to block opening of .sns files from untrusted origins.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SpacesnifferApplication
Affected:= 2.0.5.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SpaceSniffer version
    Open SpaceSniffer and check Help > About, or locate the executable (SpaceSniffer.exe) in the installation directory and view its file properties/version info
    Affected if the installed version is exactly 2.0.5.18
  2. Confirm .sns file handling is in use
    Look for any .sns snapshot files on the system (search for *.sns files) or check recent application usage for .sns file opens
    Affected if any .sns files exist on the system or have been recently opened by SpaceSniffer
  3. Check for suspicious or untrusted .sns files
    Review the source of any .sns files - check file properties, digital signatures if present, and origin of the files
    Affected if there are .sns files from untrusted or unknown sources in locations that SpaceSniffer scans or has scanned

A user is affected if SpaceSniffer version 2.0.5.18 is installed AND any .sns snapshot files from untrusted sources can be opened by the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official vendor patch is released, restrict usage of SpaceSniffer to only trusted .sns files from known sources. Consider implementing file type restrictions or application whitelisting to block opening of .sns files from untrusted origins.

Fix this in Spacesniffer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26738 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data