# CVE-2026-64619: FileCodeBox < 2.4 Anti-bruteforce Rate Limit Bypass via Spoofed Headers

> Attackers can bypass rate limits by spoofing IP headers to enumerate share codes and access other users' files without authentication.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-q7qg-rc6j-fpwp

## What is CVE-2026-64619?

CVE-2026-64619 is a high-severity vulnerability in vastsa FileCodeBox, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileCodeBox before 2.4 contains a rate-limit bypass vulnerability in the IPRateLimit class that allows unauthenticated attackers to circumvent request throttling by supplying attacker-controlled X-Real-IP and X-Forwarded-For headers without verification of trusted reverse proxy origin. Attackers can supply unique spoofed IP values on each request to enumerate all possible share codes and retrieve other users' files without authentication.

Weakness: CWE-348 (Use of Less Trusted Source)

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


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

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

## Is CVE-2026-64619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64619 is a high-severity vulnerability in vastsa FileCodeBox, published on 20 Jul 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-64619 in the wild and no public exploit code.

Affected product: vastsa FileCodeBox. 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-64619/ (Markdown: https://insights.sbomify.com/CVE-2026-64619/index.md)
```

## Sources

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

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