# CVE-2026-33582: Apache Answer: Uploading specially crafted TIFF files causes an Out-of-Memory error > An authenticated user can crash the Apache Answer server by uploading a specially crafted TIFF file that causes an out-of-memory error. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Jun 2026 - **Updated:** 9 Jun 2026 - **Also known as:** GHSA-v553-g2w6-295p, GO-2026-6153 ## What is CVE-2026-33582? CVE-2026-33582 is a medium-severity denial of service vulnerability in Apache Answer, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Unrestricted Upload of File with Dangerous Type vulnerability in Apache Answer. This issue affects Apache Answer: through 2.0.0. A crafted TIFF image could trigger excessive memory allocation during image decoding, allowing an authenticated user to cause the server process to crash. Users are recommended to upgrade to version 2.0.1, which fixes the issue. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2026-33582? 3 open source packages ship an affected version, including github.com/apache/incubator-answer and github.com/apache/answer. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/apache/incubator-answer` | Go | All versions | 1.7.2-0.20260325113131-cfc3e54f30cc | | `github.com/apache/incubator-answer` | Go | All versions | 1.7.2-0.20260325113131-cfc3e54f30cc | | `github.com/apache/answer` | Go | All versions | 1.7.2-0.20260325113131-cfc3e54f30cc | Products: Apache Answer. ## How do I fix CVE-2026-33582? Upgrade github.com/apache/incubator-answer to 1.7.2-0.20260325113131-cfc3e54f30cc or later. ## Is CVE-2026-33582 being exploited? There is no known exploitation of CVE-2026-33582 in the wild and no public exploit code. ## Other vulnerabilities in Apache Answer - [CVE-2026-60053](https://insights.sbomify.com/CVE-2026-60053/): Apache Answer: Residual Administrative API Key Access After Role or Account Revocation (critical 9.1) - [CVE-2024-22393](https://insights.sbomify.com/CVE-2024-22393/): Apache Answer: Pixel Flood Attack by uploading the large pixel file (critical 9.1) - [CVE-2026-48834](https://insights.sbomify.com/CVE-2026-48834/): Apache Answer: Denial of service via crafted Accept-Language header parsing (high 7.5) - [CVE-2026-48911](https://insights.sbomify.com/CVE-2026-48911/): Apache Answer: Unauthenticated OAuth Email-Binding Account Takeover via Existing User Confirmation Flow (high 7.5) - [CVE-2026-60023](https://insights.sbomify.com/CVE-2026-60023/): Apache Answer: Unauthorized disclosure of deleted or pending answer content (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33582 and fix it if it is affected. What it is: CVE-2026-33582 is a medium-severity denial of service vulnerability in Apache Answer, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-33582 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.7.2-0.20260325113131-cfc3e54f30cc - github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.7.2-0.20260325113131-cfc3e54f30cc - github.com/apache/answer (Go): affected all versions; fixed in 1.7.2-0.20260325113131-cfc3e54f30cc Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33582/ (Markdown: https://insights.sbomify.com/CVE-2026-33582/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33582 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33582 - OSV: https://osv.dev/vulnerability/CVE-2026-33582 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33582/ Summaries are generated and may contain mistakes; the official description above is the record.