<?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-05T21:24:38.828961+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/euvd-2026-5999</id>
    <title>EUVD-2026-5999</title>
    <updated>2026-10-05T21:24:38.879690+00:00</updated>
    <content>EUVD-2026-5999</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-5999"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-38375</id>
    <title>fkie_cve-2024-38375</title>
    <updated>2026-10-05T21:24:38.879732+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>@fastly/js-compute is a JavaScript SDK and runtime for building Fastly Compute applications. The implementation of several functions were determined to include a use-after-free bug. This bug could allow for unintended data loss if the result of the preceding functions were sent anywhere else, and often results in a guest trap causing services to return a 500. This bug has been fixed in version 3.16.0 of the `@fastly/js-compute` package.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-38375"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mp3g-vpm9-9vqv</id>
    <title>GHSA-mp3g-vpm9-9vqv — @fastly/js-compute has a use-after-free in some host call implementations</title>
    <updated>2026-10-05T21:24:38.879769+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @fastly/js-compute</p>
<p>### Impact
The implementation of the following functions were determined to include a use-after-free bug:</p>
<p>* `FetchEvent.client.tlsCipherOpensslName`
* `FetchEvent.client.tlsProtocol`
* `FetchEvent.client.tlsClientCertificate`
* `FetchEvent.client.tlsJA3MD5`
* `FetchEvent.client.tlsClientHello`
* `CacheEntry.prototype.userMetadata` of the `fastly:cache` subsystem
* `Device.lookup` of the `fastly:device` subsystem</p>
<p>This bug could allow for an unintended data leak if the result of the preceding functions were sent anywhere else, and often results in a Compute service crash causing an HTTP 500 error to be returned. As all requests to Compute are isolated from one another, the only data at risk is data present for a single request.</p>
<p>### Patches
This bug has been fixed in version 3.16.0 of the `@fastly/js-compute` package.</p>
<p>### Workarounds
There are no workarounds for this bug, any use of the affected functions introduces the possibility of a data leak or crash in guest code.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mp3g-vpm9-9vqv"/>
  </entry>
</feed>
