Skip to content
Noroxi
NVD / CVE Program· CNA Vaadin

CVE-2021-31411: Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Vaadin flow-server 6.0.0; Vaadin Vaadin 19.0.0.

Low priority for now. Upgrade to Vaadin flow-server 6.0.0; Vaadin Vaadin 19.0.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insecure temporary directory usage in frontend build functionality of com.vaadin:flow-server versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 5, 2021
Updated
Jun 16, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CNA vs NVD score

NVD
7.8
CNA · Vaadin
6.3
1.5 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-31411

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for vaadin records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vaadinflow
vaadinvaadin

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vaadin flow2.0.9 and later · before 2.5.3
  • vaadin flow3.0.0 and later · up to 5.0.0 inclusive
  • vaadin flow6.0.0 and later · up to 6.0.6 inclusive
  • vaadin vaadin14.0.3 and later · before 14.5.3
  • vaadin vaadin15.0.0 and later · before 19.0.5

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.

  • Vaadin flow-server

    • 2.0.9 and lateraffectedfixed in 6.0.0

  • Vaadin Vaadin

    • 14.0.3 and lateraffectedfixed in 19.0.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavencom.vaadin:vaadin-bomfrom 14.0.3 · before 14.5.314.5.3
Mavencom.vaadin:vaadin-bomfrom 15.0.0 · before 19.0.519.0.5

Same product

vaadin: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-31407Server classes and resources exposure in OSGi applications using Vaadin 12-14 and 19
    31Monitor
  • CVE-2021-31405Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-17
    30Monitor
  • CVE-2020-36321Directory traversal in development mode handler in Vaadin 14 and 15-17
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2021-31406Apr 23, 2021 · Timing side channel vulnerability in endpoint request handler in Vaadin 15-19
    10Monitor
  • ← EarlierCVE-2021-31408Apr 23, 2021 · Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
    28Monitor
  • Later →CVE-2021-31412Jun 24, 2021 · Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Vaadin flow-server6.0.0Vendor (CNA)
Vaadin Vaadin19.0.0Vendor (CNA)
Maven:com.vaadin:vaadin-bom14.5.3Package registry (OSV)
Maven:com.vaadin:vaadin-bom19.0.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-379 · Creation of Temporary File in Directory with Insecure Permissions

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records