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.
CVE-2026-64619
HIGHPre-NVD 7.57.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-20. the CNA's CVSS baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 10.3%
- KEV
- Not listed
Published
July 20, 2026
Last Modified
July 21, 2026
Advisory Details (3)
Auto-updated Jul 20, 2026Patch available. Sources: github_commit.
generic
FileCodeBox < 2.4 Anti-bruteforce Rate Limit Bypass via Spoofed Headers | Advisories | VulnCheck
https://www.vulncheck.com/advisories/filecodebox-anti-bruteforce-rate-limit-bypass-via-spoofed-headersgithub_commit Patch Available
commit 1b6d8e7277d3 (vastsa/FileCodeBox)
Patch available: vastsa/FileCodeBox v2.5.0 (contains commit 1b6d8e7277d3)
https://github.com/vastsa/FileCodeBox/commit/1b6d8e7277d3cfa34dc7a85803731d927b2147dageneric
[Security] Anti-bruteforce rate limit bypassed via spoofed X-Real-IP / X-Forwarded-For header, enabling anonymous enumeration of all share codes and disclosure of other users' files and text · Issue #479 · vastsa/FileCodeBox · GitHub
https://github.com/vastsa/FileCodeBox/issues/479Vendor Advisories for CVE-2026-64619(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:31 UTCEG score recompute
- 2026-07-22 23:30 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 21:37 UTCEG score recompute
- 2026-07-20 21:37 UTCGHSA enrichment
- 2026-07-20 19:13 UTCEG score recompute
- 2026-07-20 19:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-64619?
CVE-2026-64619 is a high vulnerability published on July 20, 2026. 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…
When was CVE-2026-64619 disclosed?
CVE-2026-64619 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64619 actively exploited?
CVE-2026-64619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-64619?
CVE-2026-64619 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64619, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64619
Is Your Infrastructure Affected by CVE-2026-64619?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.