# CVE-2026-48911: Apache Answer: Unauthenticated OAuth Email-Binding Account Takeover via Existing User Confirmation Flow

> Unauthenticated attackers can take over arbitrary user accounts by exploiting a missing authorization check in the OAuth email binding flow.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-47mw-vx77-gwvj

## What is CVE-2026-48911?

CVE-2026-48911 is a high-severity missing authorization vulnerability in Apache Answer, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient Verification of Data Authenticity vulnerability in Apache Answer.

This issue affects Apache Answer: through 2.0.1.

A missing authorization check in the external-login email binding flow allows unauthenticated attackers to take over arbitrary user accounts by tricking victims into clicking a crafted confirmation link.
Users are recommended to upgrade to version 2.0.2, which fixes the issue.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Apache Answer.

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

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

## Is CVE-2026-48911 being exploited?

There is no known exploitation of CVE-2026-48911 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-60023](https://insights.sbomify.com/CVE-2026-60023/): Apache Answer: Unauthorized disclosure of deleted or pending answer content (high 7.5)
- [CVE-2026-24735](https://insights.sbomify.com/CVE-2026-24735/): Apache Answer: Revision API Improper Access Control leads to Information Disclosure (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48911 is a high-severity missing authorization vulnerability in Apache Answer, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48911 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-48911/ (Markdown: https://insights.sbomify.com/CVE-2026-48911/index.md)
```

## Sources

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

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