<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 23:23:21 +0000</lastBuildDate>
    <item>
      <title>GHSA-f4xh-w4cj-qxq8 — LangSmith SDK TracingMiddleware: Arbitrary server-side file read</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f4xh-w4cj-qxq8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langsmith&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;An attacker who can send an HTTP request to a server running the LangSmith SDK&amp;#39;s `TracingMiddleware` can cause that server to read an arbitrary file from its local filesystem and upload the contents to LangSmith as a trace attachment. Depending on how the distributed trace system is deployed, triggering a read may not require authentication. Retrieving the contents requires read access to the LangSmith workspace the traces are sent to. The net effect is a trust-boundary crossing: a party with workspace trace-read access (for example a low-privilege workspace member, a contractor, or a compromised teammate account) gains the ability to read files from any server running `TracingMiddleware`, a capability outside that workspace&amp;#39;s intended trust boundary.&lt;/p&gt;
&lt;p&gt;# Impact&lt;/p&gt;
&lt;p&gt;Confidentiality (High): arbitrary read of files accessible to the server process, exposed to anyone with workspace trace-read access.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;Two defects combine. A field supplied through a tracing-propagation header was merged into the run without validation, allowing injection of run attributes including attachments (CWE-346). A type check intended to gate filesystem access did not match the type of the decoded input, so the guard never engaged (CWE-843). As a result, an attacker-named file is opened by the server and uploaded as a trace attachment by the background tracing thread (CWE-22).&lt;/p&gt;
&lt;p&gt;## Who can exploit this&lt;/p&gt;
&lt;p&gt;- Anyone reachable by HTTP can trigger the file read. Depending on how the distribute…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: langsmith&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;An attacker who can send an HTTP request to a server running the LangSmith SDK&amp;#39;s `TracingMiddleware` can cause that server to read an arbitrary file from its local filesystem and upload the contents to LangSmith as a trace attachment. Depending on how the distributed trace system is deployed, triggering a read may not require authentication. Retrieving the contents requires read access to the LangSmith workspace the traces are sent to. The net effect is a trust-boundary crossing: a party with workspace trace-read access (for example a low-privilege workspace member, a contractor, or a compromised teammate account) gains the ability to read files from any server running `TracingMiddleware`, a capability outside that workspace&amp;#39;s intended trust boundary.&lt;/p&gt;
&lt;p&gt;# Impact&lt;/p&gt;
&lt;p&gt;Confidentiality (High): arbitrary read of files accessible to the server process, exposed to anyone with workspace trace-read access.&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;Two defects combine. A field supplied through a tracing-propagation header was merged into the run without validation, allowing injection of run attributes including attachments (CWE-346). A type check intended to gate filesystem access did not match the type of the decoded input, so the guard never engaged (CWE-843). As a result, an attacker-named file is opened by the server and uploaded as a trace attachment by the background tracing thread (CWE-22).&lt;/p&gt;
&lt;p&gt;## Who can exploit this&lt;/p&gt;
&lt;p&gt;- Anyone reachable by HTTP can trigger the file read. Depending on how the distribute…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f4xh-w4cj-qxq8</guid>
    </item>
  </channel>
</rss>
