What is the CVSS score of CVE-2026-59299?

CVE-2026-59299 has a CVSS 3.1 base score of 3.5 (Low). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.1%.

Spring Cloud Function CVE-2026-59299

EUVD-2026-67185 LOW

Modification of Assumed-Immutable Data (MAID) (CWE-471)

2026-08-27 vmware

GHSA-r954-5cwm-rfh6

Java Information Disclosure Spring Spring Cloud Function

3.5

CVSS 3.1 · NVD

Severity by source

Vendor (vmware) PRIMARY

LOW

qualitative

NVD

3.5 LOW

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

vuln.today AI

3.1 LOW

Operator-level access needed to configure composition lookup (PR:H); high complexity and user interaction align with a constrained poisoning scenario with no availability impact.

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

4.0 AV:N/AC:H/AT:N/PR:H/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vmware).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVSS changed

Sep 02, 2026 - 00:52 NVD

3.1 (LOW) 3.5 (LOW)

Analysis Generated

Aug 27, 2026 - 20:51 vuln.today

DescriptionNVD

Composition lookup can potentially poison base function in Spring Cloud Function. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7 Spring Cloud Function 3.2.16 and earlier

AnalysisAI

Spring Cloud Function's composition lookup mechanism can be abused by a highly privileged attacker to poison the base function, potentially degrading the integrity and confidentiality of function execution across versions 3.2.16 and earlier through 5.0.3. The vendor-assigned CVSS base score of 3.1 reflects severely constrained exploitation prerequisites - high privilege level, high attack complexity, and required user interaction - substantially limiting realistic exposure. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

technique details hidden

Delivery

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Access

technique details hidden

Delivery

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Vulnerability AssessmentAI

Exploitation	Exploitation requires all three of the following simultaneously: (1) the Spring Cloud Function deployment must have function composition enabled and the composition lookup feature active - deployments using only simple, non-composed functions are not exposed; (2) the attacker must already hold high privileges (PR:H), meaning operator-level or equivalent access to define or influence composition lookups - a fully unauthenticated or low-privilege attacker cannot trigger the vulnerability; (3) user interaction is required (UI:R), meaning a victim must actively trigger the composed function invocation. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	Overall risk is low. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation	Consult the vendor advisory at https://spring.io/security/cve-2026-59299 for confirmed patched release versions - exact fixed version numbers are not present in the available input data and should not be assumed. … Detailed patch versions, workarounds, and compensating controls in full report.