<?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-02T11:10:36.863278+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-368103</id>
    <title>EUVD-2026-368103</title>
    <updated>2026-10-02T11:10:36.865674+00:00</updated>
    <content>EUVD-2026-368103</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-368103"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-50013</id>
    <title>fkie_cve-2026-50013</title>
    <updated>2026-10-02T11:10:36.865707+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Hoverfly is an open source API simulation tool. Prior to version 1.12.8, when Hoverfly is running in Diff mode, the `AddDiff()` function writes to the shared `responsesDiff` map without any synchronization (no mutex). When multiple proxy requests are processed concurrently (the normal case for any proxy), the concurrent map writes trigger Go's built-in race detector which causes a `fatal error: concurrent map read and map write`, immediately killing the entire Hoverfly process. This is trivially exploitable by sending multiple simultaneous requests. Version 1.12.8 patches the issue.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-50013"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-qrh4-p6v4-mrfg</id>
    <title>GHSA-qrh4-p6v4-mrfg — Hoverfly: Process Crash via Concurrent Map Write Race Condition in Diff Mode</title>
    <updated>2026-10-02T11:10:36.865742+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/SpectoLabs/hoverfly</p>
<p>### Summary:</p>
<p>When Hoverfly is running in Diff mode, the `AddDiff()` function writes to the shared `responsesDiff` map without any synchronization (no mutex). When multiple proxy requests are processed concurrently (the normal case for any proxy), the concurrent map writes trigger Go's built-in race detector which causes a `fatal error: concurrent map read and map write`, immediately killing the entire Hoverfly process. This is trivially exploitable by sending multiple simultaneous requests.</p>
<p>### Details:</p>
<p>**1. Unsynchronized map access in `AddDiff()` (`core/hoverfly_service.go:417-421`):**</p>
<p>```go
func (hf *Hoverfly) AddDiff(requestView v2.SimpleRequestDefinitionView, diffReport v2.DiffReport) {
    if len(diffReport.DiffEntries) &gt; 0 {
        diffs := hf.responsesDiff[requestView]                    // UNSYNCHRONIZED READ
        hf.responsesDiff[requestView] = append(diffs, diffReport) // UNSYNCHRONIZED WRITE
    }
}
```</p>
<p>**2. This function is called from Diff mode processing, which runs concurrently per request (`core/modes/diff_mode.go`):**</p>
<p>Each incoming proxy request is handled in its own goroutine by Go's `net/http` server. In Diff mode, each request calls `AddDiff()` after comparing the simulated and actual responses. With multiple concurrent requests, multiple goroutines write to the same map simultaneously.</p>
<p>**3. Go's runtime detects concurrent map access and terminates the process:**</p>
<p>Unlike data races on simple values (which produce undefined behavior silently),…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-qrh4-p6v4-mrfg"/>
  </entry>
</feed>
