CVE-2026-15743: CWE-524 Use of Cache Containing Sensitive Information
Catalyst::Plugin::Static::Simple versions through 0.38 for Perl mark responses as publicly cacheable. The _serve_static method always sets the Cache-Control header to "public", with no means of overriding it. This advises proxies that the content may be stored in a shared cache, and may be reused in responses to requests from other users. (This includes requests with an Authorization header.) Configuring the expires time to "0" to disable caching, as documented, is ignored.
AI Analysis
Technical Summary
The vulnerability in Catalyst::Plugin::Static::Simple (<=0.38) involves the _serve_static method forcibly setting the Cache-Control header to "public" without an option to override it. This instructs proxies and shared caches to store the response content, which may include sensitive information. Attempts to disable caching via configuration are ineffective. This leads to the risk that sensitive data could be served from shared caches to other users, violating confidentiality.
Potential Impact
Sensitive information intended for a specific user may be cached publicly and served to other users due to the forced "public" Cache-Control header. This can result in unauthorized disclosure of sensitive data through shared caches or proxy servers. The inability to disable caching exacerbates this risk.
Mitigation Recommendations
No official fix or patch is currently available for this vulnerability. Users should avoid using Catalyst::Plugin::Static::Simple versions up to 0.38 in environments where sensitive data is served. Monitor vendor advisories for updates or patches. Consider implementing additional caching controls at the proxy or server level to prevent caching of sensitive responses.
CVE-2026-15743: CWE-524 Use of Cache Containing Sensitive Information
Description
Catalyst::Plugin::Static::Simple versions through 0.38 for Perl mark responses as publicly cacheable. The _serve_static method always sets the Cache-Control header to "public", with no means of overriding it. This advises proxies that the content may be stored in a shared cache, and may be reused in responses to requests from other users. (This includes requests with an Authorization header.) Configuring the expires time to "0" to disable caching, as documented, is ignored.
Affected software
pkg:github/Catalyst-Plugin-Static-SimpleRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Catalyst::Plugin::Static::Simple (<=0.38) involves the _serve_static method forcibly setting the Cache-Control header to "public" without an option to override it. This instructs proxies and shared caches to store the response content, which may include sensitive information. Attempts to disable caching via configuration are ineffective. This leads to the risk that sensitive data could be served from shared caches to other users, violating confidentiality.
Potential Impact
Sensitive information intended for a specific user may be cached publicly and served to other users due to the forced "public" Cache-Control header. This can result in unauthorized disclosure of sensitive data through shared caches or proxy servers. The inability to disable caching exacerbates this risk.
Mitigation Recommendations
No official fix or patch is currently available for this vulnerability. Users should avoid using Catalyst::Plugin::Static::Simple versions up to 0.38 in environments where sensitive data is served. Monitor vendor advisories for updates or patches. Consider implementing additional caching controls at the proxy or server level to prevent caching of sensitive responses.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-07-14T14:24:29.805Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a8745f0acd9273b49fa84a8
Added to database: 08/20/2026, 18:22:40 UTC
Last enriched: 08/20/2026, 18:37:40 UTC
Last updated: 08/21/2026, 01:07:47 UTC
Views: 11
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.
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.