<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Apache TomEE - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/apache-tomee/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 16 Nov 2026 16:21:12 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/apache-tomee/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Apache TomEE: Request routing security constraint bypass (CVE-2026-111258)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-routing-bypass-cve-2026-111258/</link><pubDate>Mon, 16 Nov 2026 16:21:12 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-routing-bypass-cve-2026-111258/</guid><description>An improper input validation flaw in the optional request routing feature of Apache TomEE allows remote attackers to bypass security constraints and access protected resources or sensitive application files by manipulating request paths.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE contains a security vulnerability in its optional request routing feature (CVE-2026-111258). When configured, this feature forwards requests to a destination without applying the intended security constraints of that destination or the protection of the web application's private directories. An attacker can leverage this by manipulating client-controlled parts of the request path, potentially leading to unauthorized access to protected resources, application configuration files, or sensitive class files.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an unauthenticated, remote attacker to bypass access controls and perform unauthorized reads of sensitive files, including application configuration and internal Java class files. Impact is limited to installations where this specific optional routing configuration is enabled.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Audit existing Apache TomEE deployments to identify if the optional request routing feature is enabled.</li>
<li>Upgrade Apache TomEE to version 10.3.0 or 11.0.0-M2, which contain the security fixes for this vulnerability.</li>
<li>For environments using the older 1.x branch, users are advised to transition to supported versions, as the vulnerability affects versions 1.5.0 through 1.7.5.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache TomEE: Default administrative user vulnerability (CVE-2026-111257)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-default-user-cve-2026-111257/</link><pubDate>Mon, 16 Nov 2026 16:20:58 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-default-user-cve-2026-111257/</guid><description>Apache TomEE automatically generates an administrative user with a well-known password at startup when no users are defined in the default user database, allowing remote attackers to authenticate to web applications using the default realm.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE is vulnerable to an unauthorized access flaw (CVE-2026-111257) that occurs when the software is deployed with its default configuration and no users are defined in the default user database. In this state, TomEE silently adds an administrative user with a well-known password at startup.</p>
<h2 id="impact">Impact</h2>
<p>A remote attacker can use these credentials to authenticate to web applications that use the default realm and grant access to any authenticated user or to the TomEE administrative role.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache TomEE: Stateful session bean insecure temporary file handling (CVE-2026-111241)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-deserialization-cve-2026-111241/</link><pubDate>Mon, 16 Nov 2026 16:19:44 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-deserialization-cve-2026-111241/</guid><description>A vulnerability in Apache TomEE allows a local attacker to perform path hijacking in a shared temporary directory to intercept or influence deserialized stateful session bean data, potentially leading to arbitrary code execution.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE contains a security flaw in its stateful session bean passivation mechanism (CVE-2026-111241). When a non-default passivation strategy is configured, the application writes passivated bean state to predictable filenames within the shared system temporary directory. This mechanism reuses existing files, allowing a local attacker with write access to the temporary directory to perform path hijacking. The attacker can read sensitive session state or replace the file with malicious serialized data, which is then deserialized by the server upon activation. This can result in remote code execution under the privileges of the server process.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows a local attacker to read potentially sensitive session data or achieve remote code execution as the user running the Apache TomEE server process. The CVSS v3.1 base score is 7.8.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Users should upgrade to the following fixed versions to address this vulnerability:</p>
<ul>
<li>Apache TomEE 10.3.0</li>
<li>Apache TomEE 11.0.0-M2</li>
</ul>
<p>If upgrading is not immediately possible, restrict access to the system temporary directory used by the application to prevent unauthorized write access by local users.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache TomEE: Stateful session bean identifier predictability (CVE-2026-87755)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-session-hijacking-cve-2026-87755/</link><pubDate>Mon, 16 Nov 2026 16:19:14 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-session-hijacking-cve-2026-87755/</guid><description>Apache TomEE fails to use a cryptographically secure random source for stateful session bean identifiers, allowing a remote attacker with a valid session to predict and hijack other users' session states.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE contains a vulnerability where stateful session bean identifiers are generated using a cryptographically insecure random source (CVE-2026-87755). A remote attacker with access to the EJB remote endpoint and one valid session identifier can predict subsequent identifiers, enabling them to hijack active user sessions. This can result in unauthorized method invocation, as well as the modification or exposure of sensitive session data.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote attackers to perform unauthorized actions on behalf of other authenticated users, leading to potential data exposure or session state modification.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade to the patched versions of Apache TomEE to remediate this vulnerability:</p>
<ul>
<li>For the 10.x branch: Upgrade to version 10.3.0 or later.</li>
<li>For the 11.x branch: Upgrade to version 11.0.0-M2 or later.</li>
<li>For older versions (e.g., 4.x, 7.x): Evaluate migration to a supported version as these are confirmed affected.</li>
</ul>
<p>Detection teams should monitor EJB remote endpoint access logs for anomalous session identifier patterns or unauthorized method invocation attempts from suspicious source IPs.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache TomEE: EJB JAX-WS endpoint authentication bypass (CVE-2026-111263)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-auth-bypass-cve-2026-111263/</link><pubDate>Mon, 16 Nov 2026 16:18:43 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-auth-bypass-cve-2026-111263/</guid><description>Apache TomEE fails to enforce authentication for EJB JAX-WS endpoints when published within an existing web application, allowing remote unauthenticated attackers to invoke web service operations.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE contains an authentication enforcement vulnerability (CVE-2026-111263) where EJB JAX-WS endpoints fail to apply configured security when published within an existing web application. A remote unauthenticated attacker can invoke these web service operations directly. This issue occurs because the deployment descriptor authentication settings are ignored in this specific publishing context.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote, unauthenticated attackers to invoke sensitive web service operations. Impact is mitigated if the specific application already enforces authentication via web.xml security constraints or EJB method permissions.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Apache TomEE to version 10.3.0 or 11.0.0-M2 to address this vulnerability.</li>
<li>If patching is not immediately feasible, ensure that all sensitive web service endpoints are explicitly protected with web.xml security constraints or EJB method permissions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>