# CVE-2026-5233: Missing Rate Limiting in Mia Technologies' Pizzy Library

> Attackers can flood the system due to missing rate limiting in the Pizzy Library, causing denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-6554-rh36-hfh2

## What is CVE-2026-5233?

CVE-2026-5233 is a high-severity denial of service vulnerability in MIA Technology Inc. Pizzy Library, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Control of Interaction Frequency vulnerability in MIA Technology Inc. Pizzy Library allows Flooding.

This issue affects Pizzy Library: from 1.0.0.26250 before 1.3.9.26250.

Weakness: CWE-799 (Improper Control of Interaction Frequency)

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


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

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

## Is CVE-2026-5233 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5233 is a high-severity denial of service vulnerability in MIA Technology Inc. Pizzy Library, published on 15 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-5233 in the wild and no public exploit code.

Affected product: MIA Technology Inc. Pizzy Library. 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-5233/ (Markdown: https://insights.sbomify.com/CVE-2026-5233/index.md)
```

## Sources

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

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