<?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>Cpe:2.3:a:apache:tomee:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3aapachetomee/</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:32:22 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3aapachetomee/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: EJB authentication bypass via Hessian protocol (CVE-2026-97872)</title><link>https://feed.craftedsignal.io/briefs/2026-11-tomee-authentication-bypass-cve-2026-97872/</link><pubDate>Mon, 16 Nov 2026 16:32:22 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-tomee-authentication-bypass-cve-2026-97872/</guid><description>CVE-2026-97872 is an authentication bypass vulnerability in Apache TomEE where EJB endpoints exposed via the optional Hessian protocol fail to enforce security constraints, allowing remote unauthenticated invocation of methods.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>Apache TomEE contains an authentication bypass vulnerability when EJB components are exposed using the optional Hessian protocol. In affected versions, configured authentication and transport security settings are silently ignored, permitting remote unauthenticated attackers to invoke exposed EJB methods. This issue is specific to deployments utilizing the Hessian module.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows remote, unauthenticated attackers to invoke EJB methods, potentially leading to unauthorized operations within the affected web application. The CVSS v3.1 base score is 7.5.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Administrators should identify all instances of Apache TomEE where the Hessian module is enabled. Until an official patch is available, block network access to Hessian endpoints from untrusted clients. Alternatively, migrate to a more secure remoting protocol if the Hessian module is not strictly required for application functionality.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Apache Derby: Network service bind address bypass (CVE-2026-97849)</title><link>https://feed.craftedsignal.io/briefs/2026-11-derby-network-bind-cve-2026-97849/</link><pubDate>Mon, 16 Nov 2026 16:31:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-derby-network-bind-cve-2026-97849/</guid><description>The embedded Apache Derby network service ignores configured bind address settings, causing it to expose the database on all network interfaces, allowing remote attackers to read or modify data.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>The embedded Apache Derby network service contains a flaw where it ignores configured bind address settings, resulting in the service listening on all network interfaces regardless of user intent. This misconfiguration exposes the database to remote network access. Attackers can connect to the database service to perform unauthorized data read and write operations.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows unauthenticated remote attackers with network connectivity to access the database, posing a critical risk of data exfiltration or modification. The CVSS 3.1 base score is 9.1.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade Apache TomEE components to versions that address this vulnerability. For the <code>org.apache.tomee:openejb-derbynet</code> package, upgrade to 10.3.0 or 11.0.0-M2 or later. If upgrading is not immediately possible, restrict network access to the database service at the network perimeter or firewall level to prevent unauthorized remote connections.</p>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category></item><item><title>Apache TomEE: Authentication bypass in OpenEJB embedded HTTP server (CVE-2026-111256)</title><link>https://feed.craftedsignal.io/briefs/2026-11-openejb-auth-bypass-cve-2026-111256/</link><pubDate>Mon, 16 Nov 2026 16:20:45 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-openejb-auth-bypass-cve-2026-111256/</guid><description>The embedded OpenEJB HTTP server in certain Apache TomEE configurations fails to enforce configured authentication methods for JAX-WS or JAX-RS endpoints, allowing unauthenticated remote access.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>CVE-2026-111256 affects Apache TomEE when JAX-WS or JAX-RS endpoints are published by the embedded OpenEJB HTTP server instead of Tomcat. In these instances, configured authentication methods are silently ignored, causing the endpoint to be published without authentication. This vulnerability only applies to deployments that use the embedded HTTP server and rely on such an authentication method.</p>
<h2 id="impact">Impact</h2>
<p>A remote unauthenticated attacker can invoke the exposed JAX-WS or JAX-RS operations without credentials.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat-based TomEE distributions. No specific fixed version information is currently provided by the source.</p>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>authentication-bypass</category><category>web-server</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>