# CVE-2026-64945: Apache Answer: Incorrect permission mapping allows users with only the unpin permission to hide/show questions

> Users with only unpin permissions can hide or show questions due to incorrect permission checks in custom role configurations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-4242-4jmj-g584

## What is CVE-2026-64945?

CVE-2026-64945 is a missing authorization vulnerability in Apache Answer, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Apache Answer.

This issue affects Apache Answer: through 2.0.2.

The question operation controller gates hide/show operations on the wrong permission check result (the unpin permission instead of the hide permission), so in custom role configurations that separate these permissions, a user granted only question.unpin can hide or restore questions without holding question.hide or question.show.

Users are recommended to upgrade to version 2.0.3, which fixes the issue.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-64945?


## How do I fix CVE-2026-64945?

No fix has been published for CVE-2026-64945 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-64945 being exploited?

There is no known exploitation of CVE-2026-64945 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64945 and fix it if it is affected.

What it is: CVE-2026-64945 is a missing authorization vulnerability in Apache Answer, published on 19 Oct 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-64945 in the wild and no public exploit code.

Affected product: Apache Answer. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-64945/ (Markdown: https://insights.sbomify.com/CVE-2026-64945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64945
- OSV: https://osv.dev/vulnerability/CVE-2026-64945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64945/
Summaries are generated and may contain mistakes; the official description above is the record.