Cyber Resilience

CVE-2026-47882

Published
30 July 2026
Modified
01 August 2026
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0017 7th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-47882 is a high-severity PRNG (CWE-338) vulnerability in Spring Boot DevTools (inferred from references). Its CVSS base score is 8.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

When enabling Spring Boot DevTools support for a remote application target (for example a Docker container or Cloud Foundry app) from the Spring Tools Boot Dashboard, Spring Tools generates a shared secret that authenticates DevTools remote-restart uploads to the deployed…

more

application. This secret was generated using a non-cryptographic pseudo-random number generator rather than a cryptographically secure source of randomness. Affected Spring Products and Versions: Spring Tools for Eclipse: 5.2.0 and earlier

CWE(s)
CWE-338

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
attack.mitre.org →
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-36993Shared CWE-338
CVE-2023-31305Shared CWE-338
CVE-2023-48224Shared CWE-338
CVE-2025-69217Shared CWE-338
CVE-2024-7315Shared CWE-338
CVE-2026-56141Shared CWE-338
CVE-2024-57835Shared CWE-338
CVE-2026-14495Shared CWE-338
CVE-2025-68932Shared CWE-338
CVE-2026-40514Shared CWE-338

Affected Assets

Spring
Boot DevTools
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Requiring specific approved cryptography for protection directly mandates use of strong PRNGs instead of weak ones.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles applied during design and development include selection of cryptographically strong random number generation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require cryptographically strong RNG selection and usage in security contexts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandates use of approved cryptographic controls, directly requiring cryptographically strong RNGs.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect use of weak random number generators.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes should catch weak PRNG usage during design and code review.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographically strong random number generation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure engineering principles include selection of appropriate cryptographic primitives.

A.8.28 Secure coding partial match
prevents

Secure coding standards prohibit use of weak PRNGs in security contexts.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-338
RHEL 8 (1 rule)
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-338
Ubuntu 22.04 (1 rule)
  • V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-338

References