VMware Spring Integration up to 7.1.0 PropertiesPersistingMetadataStore metadata-store.properties permission assignment

Summaryinfo

A vulnerability classified as problematic has been found in VMware Spring Integration up to 5.5.21/6.4.12/6.5.10/7.0.5/7.1.0. This issue affects some unknown processing of the file spring-integration/metadata-store.properties of the component PropertiesPersistingMetadataStore. This manipulation causes permission assignment. This vulnerability is tracked as CVE-2026-59292. The attack is restricted to local execution. No exploit exists.

Detailsinfo

A vulnerability was found in VMware Spring Integration up to 5.5.21/6.4.12/6.5.10/7.0.5/7.1.0. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the file spring-integration/metadata-store.properties of the component PropertiesPersistingMetadataStore. The manipulation with an unknown input leads to a permission assignment vulnerability. The CWE definition for the vulnerability is CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. As an impact it is known to affect confidentiality. The summary by CVE is:

PropertiesPersistingMetadataStore, the default file-based ConcurrentMetadataStore, persists its state to ${java.io.tmpdir}/spring-integration/metadata-store.properties with world-readable permissions. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12 Spring Integration 5.5.21 and earlier

It is possible to read the advisory at spring.io. This vulnerability is known as CVE-2026-59292 since 07/04/2026. The exploitation appears to be easy. Attacking locally is a requirement. Additional levels of successful authentication are required for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/27/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• VMware

Name

• Spring Integration

Version

• 5.5.0
• 5.5.1
• 5.5.2
• 5.5.3
• 5.5.4
• 5.5.5
• 5.5.6
• 5.5.7
• 5.5.8
• 5.5.9
• 5.5.10
• 5.5.11
• 5.5.12
• 5.5.13
• 5.5.14
• 5.5.15
• 5.5.16
• 5.5.17
• 5.5.18
• 5.5.19
• 5.5.20
• 5.5.21
• 6.4.0
• 6.4.1
• 6.4.2
• 6.4.3
• 6.4.4
• 6.4.5
• 6.4.6
• 6.4.7
• 6.4.8
• 6.4.9
• 6.4.10
• 6.4.11
• 6.4.12
• 6.5.0
• 6.5.1
• 6.5.2
• 6.5.3
• 6.5.4
• 6.5.5
• 6.5.6
• 6.5.7
• 6.5.8
• 6.5.9
• 6.5.10
• 7.0
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.1.0

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion