CVE-2026-50787 e-SIC Livre (esiclivre) v0.2.2 and earlier contains an uncontrolled resource consumption vulnerability in restrito/inc/captcha.php.
High 7.5
Published
Updated
Check this codebase for CVE-2026-50787 and fix it if it is affected.
What it is: CVE-2026-50787 is a high-severity vulnerability in n/a, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-50787 in the wild and no public exploit code.
Affected product: n/a. 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-50787/ (Markdown: https://insights.sbomify.com/CVE-2026-50787/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-50787?
CVE-2026-50787 is a high-severity vulnerability in n/a, published on 23 Oct 2026.
Official description
e-SIC Livre (esiclivre) v0.2.2 and earlier contains an uncontrolled resource consumption vulnerability in restrito/inc/captcha.php. The application uses user-supplied parameters (l, a, tf, ql) without validation to generate CAPTCHA images, allowing remote attackers to cause denial of service via excessive memory and CPU consumption.
Weakness: CWE-400
Which versions are affected by CVE-2026-50787?
How do I fix CVE-2026-50787?
No fix has been published for CVE-2026-50787 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-50787 being exploited?
There is no known exploitation of CVE-2026-50787 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-x2cv-c5p2-8w76.