# CVE-2024-26578: Apache Answer: Repeated submission at registration created duplicate users with the same name

> Attackers can create duplicate user accounts with identical names by rapidly submitting registration requests, compromising data integrity.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** Yes
- **Published:** 22 Feb 2024
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-9q24-hwmc-797x, GO-2024-2580

## What is CVE-2024-26578?

CVE-2024-26578 is a medium-severity vulnerability in Apache Answer, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in Apache Answer.This issue affects Apache Answer: through 1.2.1.

Repeated submission during registration resulted in the registration of the same user. When users register, if they rapidly submit multiple registrations using scripts, it can result in the creation of multiple user accounts simultaneously with the same name.
Users are recommended to upgrade to version [1.2.5], which fixes the issue.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-26578?

3 open source packages ship an affected version, including github.com/apache/incubator-answer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.5 |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.5 |
| `github.com/apache/incubator-answer` | Go | All versions | 1.2.5 |

Products: Apache Answer.

## How do I fix CVE-2024-26578?

Upgrade github.com/apache/incubator-answer to 1.2.5 or later.

## Is CVE-2024-26578 being exploited?

There is no known exploitation of CVE-2024-26578 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-2024-26578 and fix it if it is affected.

What it is: CVE-2024-26578 is a medium-severity vulnerability in Apache Answer, published on 22 Feb 2024. 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-2024-26578 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.2.5
- github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.2.5
- github.com/apache/incubator-answer (Go): affected all versions; fixed in 1.2.5

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

## Sources

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

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