TiffApplication · Golang
CVE-2026-33809
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 · uneditedA maliciously crafted TIFF file can cause image decoding to attempt to allocate up 4GiB of memory, causing either excessive resource consumption or an out-of-memory error.
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 · high confidenceA vulnerability in TIFF image file decoding allows a specially crafted TIFF file to trigger excessive memory allocation attempts of up to 4GiB, leading to resource exhaustion or out-of-memory conditions.
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
TiffApplication
< 0.38.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Golang Tiff library is in useRun 'go mod graph | grep tiff' or 'go list -m all' to list all dependencies and search for the tiff packageAffected if The tiff package appears in your dependency graph
-
Confirm the installed versionRun 'go list -m -versions github.com/go-tiff/tiff' to see available versions, then compare against your installed version shown in 'go list -m all'Affected if Your installed version is lower than 0.38.0 (e.g., 0.37.0, 0.36.0, etc.)
-
Verify TIFF decoding is actively usedSearch your codebase for calls to tiff.Decode, DecodeTile, or related decoding functions from the tiff packageAffected if Your code calls any tiff decoding functions to process TIFF image files
-
Check if untrusted TIFF input is processedInspect your application to determine whether it accepts or processes TIFF files from external or untrusted sourcesAffected if Your application decodes TIFF files from user input, uploaded files, or network sources
-
Identify the process handling TIFF filesLocate the specific code path and the binary/executable that performs TIFF decodingAffected if A Go binary or service in your environment processes TIFF images using the vulnerable library version
You are affected if your environment uses a Golang Tiff library version below 0.38.0 and processes TIFF files through that library.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped0.38.0
Implement strict memory allocation limits during TIFF decoding and validate image dimensions before allocating buffers to prevent unbounded memory requests.
tiff v0.38.0
- Check the current tiff library version in use (go list -m all | grep tiff or check go.mod)
- Upgrade to tiff version 0.38.0 or later using: go get github.com/go-graphics/[email protected] or go get -u github.com/go-graphics/tiff
- Verify the upgrade was successful by running: go list -m all | grep tiff
- Run existing tests to verify the upgrade does not break functionality
- Rebuild and deploy the application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tiff
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33809 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33809 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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