Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2021-31405: 1.13% estimated exploitation activity in the next 30 days; percentile 66.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Unsafe validation RegEx in EmailField component in com.vaadin:vaadin-text-field-flow versions 2.0.4 through 2.3.2 (Vaadin 14.0.6 through 14.4.3), and 3.0.0 through 4.0.2 (Vaadin 15.0.0 through 17.0.10) allows attackers to cause uncontrolled resource consumption by submitting malicious email addresses. - https://vaadin.com/security/cve-2021-31405

Published by the source

19 Apr 2021, 14:47 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2wqp-jmcc-mc77

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-31405

Advisory: Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17
IDs: CVE-2021-31405, GHSA-2wqp-jmcc-mc77
Record: https://patchnext.com/advisories/cve-2021-31405 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.vaadin:vaadin-bom 17.0.11, 14.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.vaadin:vaadin-bom: affected >= 14.0.6, < 14.4.4; >= 15.0.0, < 17.0.11; fixed in 14.4.4, 17.0.11

## Suggested inspection (read-only)
- Maven com.vaadin:vaadin-bom: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.vaadin:vaadin-bom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2wqp-jmcc-mc77 (GitHub-reviewed advisory GHSA-2wqp-jmcc-mc77 lists affected ranges: Maven com.vaadin:vaadin-bom >=14.0.6 =15.0.0 <17.0.11)

Commands are suggestions: review each one before running it.