<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T23:20:31.824726+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2025-3048</id>
    <title>CVE-2025-3048 — Path Traversal in AWS SAM CLI allows file copy to local cache</title>
    <updated>2026-10-08T23:20:31.828282+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AWS Serverless Application Model Command Line Interface</p>
<p>After completing a build with AWS Serverless Application Model Command Line Interface (SAM CLI) which include symlinks, the content of those symlinks are copied to the cache of the local workspace as regular files or directories. As a result, a user who does not have access to those symlinks outside of the Docker container would now have access via the local workspace.</p>
<p>Users should upgrade to version 1.134.0 and ensure any forked or derivative code is patched to incorporate the new fixes. After upgrading, users must re-build their applications using the sam build --use-container to update the symlinks.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2025-3048"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pp64-wj43-xqcr</id>
    <title>GHSA-pp64-wj43-xqcr — AWS SAM CLI Path Traversal allows file copy to local cache</title>
    <updated>2026-10-08T23:20:31.828338+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: aws-sam-cli</p>
<p>### Summary</p>
<p>The [AWS Serverless Application Model Command Line Interface (AWS SAM CLI)](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli.html) is an open-source CLI tool that helps Lambda developers to build and develop Lambda applications locally on their computers using Docker.</p>
<p>After completing a build with AWS SAM CLI which include symlinks, the content of those symlinks are copied to the cache of the local workspace as regular files or directories. As a result, a user who does not have access to those symlinks outside of the Docker container would now have access via the local workspace.</p>
<p>Users should [upgrade to v1.134.0 or newer](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/manage-sam-cli-versions.html#manage-sam-cli-versions-upgrade) and ensure any forked or derivative code is patched to incorporate the new fixes. After upgrading, users must re-build their applications using the `sam build --use-container` to update the symlinks.</p>
<p>### Impact</p>
<p>The issue is limited to the local workspace and does not affect AWS services, production environments or cross-account resources. The issue only affects workspaces using the AWS SAM CLI with container builds (--use-container), potentially allowing access to content of linked files in the SAM CLI cache.</p>
<p>**Impacted versions:** &lt;= AWS SAM CLI v1.133.0</p>
<p>### Patches</p>
<p>The patches are included in AWS SAM CLI  version to v1.134.0 and newer. Users shoul…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pp64-wj43-xqcr"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-1206</id>
    <title>PYSEC-2026-1206 — AWS SAM CLI Path Traversal allows file copy to local cache</title>
    <updated>2026-10-08T23:20:31.828384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: aws-sam-cli</p>
<p>### Summary</p>
<p>The [AWS Serverless Application Model Command Line Interface (AWS SAM CLI)](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli.html) is an open-source CLI tool that helps Lambda developers to build and develop Lambda applications locally on their computers using Docker.</p>
<p>After completing a build with AWS SAM CLI which include symlinks, the content of those symlinks are copied to the cache of the local workspace as regular files or directories. As a result, a user who does not have access to those symlinks outside of the Docker container would now have access via the local workspace.</p>
<p>Users should [upgrade to v1.134.0 or newer](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/manage-sam-cli-versions.html#manage-sam-cli-versions-upgrade) and ensure any forked or derivative code is patched to incorporate the new fixes. After upgrading, users must re-build their applications using the `sam build --use-container` to update the symlinks.</p>
<p>### Impact</p>
<p>The issue is limited to the local workspace and does not affect AWS services, production environments or cross-account resources. The issue only affects workspaces using the AWS SAM CLI with container builds (--use-container), potentially allowing access to content of linked files in the SAM CLI cache.</p>
<p>**Impacted versions:** &lt;= AWS SAM CLI v1.133.0</p>
<p>### Patches</p>
<p>The patches are included in AWS SAM CLI  version to v1.134.0 and newer. Users shoul…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-1206"/>
  </entry>
</feed>
