Skip to main content
Menu
CVEs

erupt excessive memory allocation in CAPTCHA endpoint

CVE-2026-133609EUVD-2026-131562Published , updated

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

The erupts erupt software, up to version 2.0.2, has a flaw in its CAPTCHA endpoint that lets an attacker remotely, without logging in, make the server allocate uncontrolled amounts of memory by manipulating the height value. Upgrading to a fixed release (2.0.3 or later) resolves the issue.

Written by a model

Original description

A vulnerability was found in erupts erupt up to 2.0.2. This impacts the function EruptUserController.createCode of the file erupt-upms/src/main/java/xyz/erupt/upms/controller/EruptUserController.java of the component UPMS CAPTCHA Endpoint. Performing a manipulation of the argument height results in uncontrolled memory allocation. The attack may be initiated remotely. Upgrading to version 2.0.3 will fix this issue. The patch is named fc59a6eece991ff5aced363243d0b2d14f73ed95. It is recommended to upgrade the affected component.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133609 (erupts erupt UPMS CAPTCHA Endpoint EruptUserController.java EruptUserController.createCode memory allocation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133609 (entry last updated 2026-11-20):
Affected:
- erupts erupt: versions 2.0.0, 2.0.1, 2.0.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133609 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133609 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/erupts/erupt/pull/357
- https://github.com/erupts/erupt/commit/fc59a6eece991ff5aced363243d0b2d14f73ed95
- https://github.com/erupts/erupt/releases/tag/2.0.3
- https://github.com/erupts/erupt/issues/353
- https://vuldb.com/vuln/441154
- https://vuldb.com/vuln/441154/cti
- https://vuldb.com/cve/CVE-2026-133609
- https://vuldb.com/submit/1050071
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133609
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133609"}.

Affected versions

cve.now Index

27Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 11

Questions about CVE-2026-133609

Is CVE-2026-133609 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133609?

erupt: versions 2.0.0, 2.0.1, 2.0.2.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.