# CVE-2026-55624: MintyItanium Lost-Auction takes items like barrier blocks out from search GUI

> Players can exploit the auction GUI to steal restricted items or duplicate inventory, requiring plugin updates to prevent economic abuse.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 25 Aug 2026
- **Updated:** 25 Aug 2026

## What is CVE-2026-55624?

CVE-2026-55624 is a medium-severity vulnerability in MintyItanium Lost-Auction, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MintyItanium Lost-Auction is an auction plugin for Minecraft. Prior to commit 88c920b05042929db334ba06d57f052b42d6b3f8, players can take items like barrier blocks or duplicate items from the GUI. Commit 88c920b05042929db334ba06d57f052b42d6b3f8 fixes the issue.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

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


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

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

## Is CVE-2026-55624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55624 is a medium-severity vulnerability in MintyItanium Lost-Auction, published on 25 Aug 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-55624 in the wild and no public exploit code.

Affected product: MintyItanium Lost-Auction. 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-55624/ (Markdown: https://insights.sbomify.com/CVE-2026-55624/index.md)
```

## Sources

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

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