CWE-552: Files or Directories Accessible to External Parties
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Last updated
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Last updated
Web servers, FTP servers, and similar servers may store a set of files underneath a "root" directory that is accessible to the server's users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories. In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.
444 recorded CVEs are caused by CWE-552 (Files or Directories Accessible to External Parties), including 5 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 100 new CWE-552 CVEs have been recorded so far in 2026 (66 in 2025).
Apache Flink directory traversal attack: reading remote files through the REST API
Gladinet CentreStack and TrioFox Local File Inclusion Flaw
Toptech TMS7 and TopHAT Files or Directories Accessible to External Parties
Mounted Kubernetes Secrets under a predictable path located within the web server document root
Gogs deletion of internal files allows remote command execution
Files or Directories Accessible to External Parties in Splunk SOAR
Gogs allows deletion of internal files
Logged-in Administrator may get unrestricted file system access
Files Accessible to External Parties in Opencast
Showing 12 of 444 recorded CWE-552 CVEs. Get an alert for each new one, with AI-written analysis and fixes.
Monitor these CVEsWhat can happen when CWE-552 is exploited.
Read Files or Directories, Modify Files or Directories
Affects: Confidentiality, Integrity
Typically introduced during these phases of the software lifecycle.
Technologies
Practical mitigations for CWE-552, grouped by where in the lifecycle they apply.
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
MITRE examples of the weakness in code.
The following Azure command updates the settings for a storage account:
Vulnerable example
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access trueSafe example
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access falseThe following Google Cloud Storage command gets the settings for a storage account named 'BUCKET_NAME':
Example
gsutil iam get gs://BUCKET_NAMEVulnerable example
"bindings":[{
"members":[
"projectEditor: PROJECT-ID",
"members":[
"allUsers",Real CVEs that MITRE cites as examples of this weakness.
CAPEC attack patterns that exploit this weakness.
Common questions about CWE-552.
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Get an alert when a new CWE-552 CVE affects your products, with AI-written analysis and remediation steps.