CVE-2026-59292 json
World-readable metadata file in PropertiesPersistingMetadataStore (insecure temp-file permissions)
published 2026-08-27 2 mo ago modified 2026-08-31 2 mo ago also EUVD-2026-67180
- cvss
- 3.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- vmware spring_integration 5.5.22, 6.4.13, 6.5.11, 7.0.5.1, 7.1.0.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-59292 updated cvss 3.3
org.springframework.integration/spring-integration-core: Spring Integration: Information disclosure via world-readable metadata file
-
Red Hat Fuse 7 spring-integration-core 4.2.9.RELEASEaffected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N |
Affected products
- Spring Spring Integration
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
spring.io
/security/cve-2026-59292
vendor-advisory
Sources
- CVE List CVE-2026-59292
- NVD CVE-2026-59292
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.