<?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>Tue, 06 Oct 2026 15:11:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342151</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342151</link>
      <description>EUVD-2026-342151</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342151</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43910</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43910</link>
      <description>&lt;p&gt;Appium Java Client is the Java language binding for writing Appium tests that conform to the W3C WebDriver protocol. From 8.2.1 until 10.1.1, when directConnect(true) is enabled, AppiumCommandExecutor.setDirectConnect() reads the directConnectHost, directConnectPort, and directConnectPath fields from the server&amp;#39;s NEW_SESSION response and rebuilds the client&amp;#39;s server URL from them, validating only that the protocol is https, with no host allowlist or IP validation; a rogue or compromised server can therefore redirect all subsequent session traffic to an arbitrary destination, enabling full interception of session traffic and a server-side request forgery pivot to internal hosts, including cloud metadata (IMDS) credential theft. This vulnerability is fixed in 10.1.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Appium Java Client is the Java language binding for writing Appium tests that conform to the W3C WebDriver protocol. From 8.2.1 until 10.1.1, when directConnect(true) is enabled, AppiumCommandExecutor.setDirectConnect() reads the directConnectHost, directConnectPort, and directConnectPath fields from the server&amp;#39;s NEW_SESSION response and rebuilds the client&amp;#39;s server URL from them, validating only that the protocol is https, with no host allowlist or IP validation; a rogue or compromised server can therefore redirect all subsequent session traffic to an arbitrary destination, enabling full interception of session traffic and a server-side request forgery pivot to internal hosts, including cloud metadata (IMDS) credential theft. This vulnerability is fixed in 10.1.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43910</guid>
    </item>
    <item>
      <title>GHSA-28f5-38xr-jh2w — java-client Allows Network Pivot via Unvalidated directConnect Redirect in AppiumCommandExecutor</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-28f5-38xr-jh2w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.appium:java-client&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When `directConnect(true)` is enabled, appium/java-client unconditionally
accepts `directConnectHost`, `directConnectPort`, and `directConnectPath`
from the server&amp;#39;s NEW_SESSION response and silently redirects all subsequent
session traffic to the attacker-specified endpoint — with no allowlist,
no host validation, and no user notification.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;- `AppiumCommandExecutor.java` (line 196–219): `setDirectConnect()` builds
  a new URL from server-supplied fields and calls `overrideServerUrl(newUrl)`
  without validating host/IP.
- `DirectConnect.java`: `getUrl()` constructs `protocol://host:port/path`
  with no allowlist.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Only the protocol is validated (must equal &amp;#34;https&amp;#34;). The destination host
and port are never checked against any allowlist or denylist.&lt;/p&gt;
&lt;p&gt;## PoC (confirmed)&lt;/p&gt;
&lt;p&gt;A rogue server injecting `directConnectHost=127.0.0.1:4443` causes the
client to silently redirect all post-session commands:&lt;/p&gt;
&lt;p&gt;[bootstrap]       POST /wd/hub/session
[bootstrap]       Injecting directConnect -&amp;gt; https://127.0.0.1:4443/wd/hub
[redirect-target] HIT #1: GET /wd/hub/session/poc-session-001/source
[redirect-target] HIT #2: DELETE /wd/hub/session/poc-session-001&lt;/p&gt;
&lt;p&gt;Original source code unmodified — confirmed via `git diff HEAD` (empty).&lt;/p&gt;
&lt;p&gt;## Evidence Screenshots&lt;/p&gt;
&lt;p&gt;**Screenshot 1 — Rogue server capturing redirected traffic:**&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;887&amp;#34; height=&amp;#34;146&amp;#34; alt=&amp;#34;1&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/cc28002c-ea20-4ac8-8336-cec632e3c842&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;**Screen…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.appium:java-client&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When `directConnect(true)` is enabled, appium/java-client unconditionally
accepts `directConnectHost`, `directConnectPort`, and `directConnectPath`
from the server&amp;#39;s NEW_SESSION response and silently redirects all subsequent
session traffic to the attacker-specified endpoint — with no allowlist,
no host validation, and no user notification.&lt;/p&gt;
&lt;p&gt;## Affected Code&lt;/p&gt;
&lt;p&gt;- `AppiumCommandExecutor.java` (line 196–219): `setDirectConnect()` builds
  a new URL from server-supplied fields and calls `overrideServerUrl(newUrl)`
  without validating host/IP.
- `DirectConnect.java`: `getUrl()` constructs `protocol://host:port/path`
  with no allowlist.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Only the protocol is validated (must equal &amp;#34;https&amp;#34;). The destination host
and port are never checked against any allowlist or denylist.&lt;/p&gt;
&lt;p&gt;## PoC (confirmed)&lt;/p&gt;
&lt;p&gt;A rogue server injecting `directConnectHost=127.0.0.1:4443` causes the
client to silently redirect all post-session commands:&lt;/p&gt;
&lt;p&gt;[bootstrap]       POST /wd/hub/session
[bootstrap]       Injecting directConnect -&amp;gt; https://127.0.0.1:4443/wd/hub
[redirect-target] HIT #1: GET /wd/hub/session/poc-session-001/source
[redirect-target] HIT #2: DELETE /wd/hub/session/poc-session-001&lt;/p&gt;
&lt;p&gt;Original source code unmodified — confirmed via `git diff HEAD` (empty).&lt;/p&gt;
&lt;p&gt;## Evidence Screenshots&lt;/p&gt;
&lt;p&gt;**Screenshot 1 — Rogue server capturing redirected traffic:**&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;887&amp;#34; height=&amp;#34;146&amp;#34; alt=&amp;#34;1&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/cc28002c-ea20-4ac8-8336-cec632e3c842&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;**Screen…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-28f5-38xr-jh2w</guid>
    </item>
  </channel>
</rss>
