CVE-2026-59292: CWE-732 Incorrect Permission Assignment for Critical Resource in Spring Spring Integration
Description
CVE-2026-59292 is a low severity vulnerability in Spring Integration where the default file-based ConcurrentMetadataStore persists its state to a file with world-readable permissions. This incorrect permission assignment could expose sensitive metadata to unauthorized local users. The issue affects multiple versions of Spring Integration including 5.5.21 and earlier, 6.4.0 through 6.4.12, 6.5.0 through 6.5.10, 7.0.0 through 7.0.5, and 7.1.0. No official patch or remediation guidance has been provided yet.
CVSS v3.1
Score 3.2low
Affected software
Spring
Spring Integration
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-59292 involves the PropertiesPersistingMetadataStore component in Spring Integration, which persists its state to a file located at ${java.io.tmpdir}/spring-integration/metadata-store.properties. This file is created with world-readable permissions, constituting an incorrect permission assignment (CWE-732). This could allow unauthorized local users to read potentially sensitive metadata stored by the application. The affected versions include Spring Integration 5.5.21 and earlier, 6.4.0 through 6.4.12, 6.5.0 through 6.5.10, 7.0.0 through 7.0.5, and 7.1.0. The CVSS 3.1 base score is 3.2, indicating low severity, with an attack vector of local access, low complexity, and requiring high privileges. There is no vendor advisory or patch information available at this time.
Potential Impact
The impact is limited to unauthorized local users potentially reading the metadata stored in the file due to world-readable permissions. This could lead to information disclosure of metadata state persisted by Spring Integration. There is no indication of integrity or availability impact. The vulnerability requires local access and high privileges to exploit, reducing its overall risk.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting access to the temporary directory or the specific metadata-store.properties file to prevent unauthorized local access. Monitoring and controlling local user permissions can help mitigate exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-07-04T18:13:34.323Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a909cf8acd9273b49b2d058
Added to database: 08/27/2026, 20:24:24 UTC
Last enriched: 09/10/2026, 04:23:29 UTC
Last updated: 10/11/2026, 18:48:20 UTC
Views: 89
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.