CVE
CVE-2026-86336, CVE-2026-111244, CVE-2026-111257, CVE-2026-111261, CVE-2026-111264, CVE-2026-86811, CVE-2026-87755, CVE-2026-87756, CVE-2026-87758, CVE-2026-97849, CVE-2026-97867, CVE-2026-111240, CVE-2026-111241, CVE-2026-111242, CVE-2026-111245, CVE-2026-111247, CVE-2026-111251, CVE-2026-111258, CVE-2026-111259, CVE-2026-111262, CVE-2026-111263, CVE-2026-86532, CVE-2026-111243, CVE-2026-111248, CVE-2026-111249, CVE-2026-111260, CVE-2026-86531, CVE-2026-97870, CVE-2026-97872, CVE-2026-97874, CVE-2026-97880, CVE-2026-97881, CVE-2026-97888, CVE-2026-111239, CVE-2026-111250, CVE-2026-111256, CVE-2026-97890, CVE-2026-111246, CVE-2026-126837, CVE-2026-126835, CVE-2026-119179, CVE-2026-127109, CVE-2026-102643, CVE-2026-123817, CVE-2026-127056, CVE-2026-126190, CVE-2026-126191, CVE-2026-125271, CVE-2026-126087, CVE-2026-128124, CVE-2026-128125, CVE-2026-128126, CVE-2026-128127, CVE-2026-128128, CVE-2026-128129, CVE-2026-128130, CVE-2026-128131, CVE-2026-128132
CWE
CWE-862, CWE-863, CWE-1392, CWE-287, CWE-288, CWE-22, CWE-180, CWE-201, CWE-94, CWE-770, CWE-407, CWE-1333, CWE-426
Affected Surface
- Apache TomEE before 10.3.0 and 11.0.0-M1 before 11.0.0-M2 (`org.apache.tomee:tomee-catalina`, `openejb-core`, `mp-jwt`, `tomee-security`, `tomee-webservices` and related artifacts), with some issues reaching back to OpenEJB 4.x and TomEE 1.5
- Apache TomEE optional modules `openejb-http`, `openejb-hessian`, `openejb-ssh` and `openejb-common-cli` (12 CVEs, no fixed version; removed in 10.3.0 and 11.0.0-M2)
- npm `mongodb` (MongoDB Node.js driver) from 3.3.3 before 7.8.0 when using `mongodb+srv://` (`CVE-2026-126837`), from 6.7.0 before 7.9.0 when combining `ENVIRONMENT` with `OIDC_CALLBACK` / `OIDC_HUMAN_CALLBACK` (`CVE-2026-126835`), and 6.11.0 before 6.22.0 / 7.0.0 before 7.8.0 when using `timeoutMS` (`CVE-2026-119179`)
- npm `promzard` 4.0.0 and earlier (`CVE-2026-127109`, no fixed release)
- PyPI `asyncssh` before 2.24.1 (`CVE-2026-102643`), `aiohttp` before 3.14.4 (`CVE-2026-123817` and `CVE-2026-128124` through `CVE-2026-128132`), `soupsieve` before 4.0 (`CVE-2026-126190`) and before 3.0 (`CVE-2026-126191`), `awslabs.aws-api-mcp-server` 0.2.13 before 1.5.1 (`CVE-2026-125271`), and `openjd-sessions` before 0.11.0 / AWS Deadline Cloud worker agent before 0.33.0 (`CVE-2026-126087`)
- npm `papaparse` before 5.7.1 (`CVE-2026-127056`)
Update, 14 November 2026 (nine more aiohttp 3.14.4 CVEs): NVD published nine more CVEs on 13 November, CVE-2026-128124 through CVE-2026-128132, all fixed in the same aiohttp 3.14.4 release this roundup already covers for CVE-2026-123817. The aio-libs maintainers had posted the matching GitHub advisories on 8 November. Debian tracks them in bug 1153954, and on 14 November its tracker still listed every python-aiohttp package from bookworm to sid as vulnerable. Seven of the nine CVE records score CVSS 4.0 8.2 to 8.7, though the maintainers’ own advisories rate only CVE-2026-128128 as high and the rest medium or low. All nine are denial-of-service bugs: a single unauthenticated request or WebSocket peer can stall the event loop or drive memory use past the limits aiohttp is configured with.
| CVE | GHSA | CVSS | What a remote peer can do |
|---|---|---|---|
CVE-2026-128126 | GHSA-xgw8-8ccx-rmqh | 4.0: 8.7 | Block the event loop with a URL-encoded form full of repeated keys sent to a handler that calls Request.post() (quadratic MultiDict inserts) |
CVE-2026-128127 | GHSA-24c4-3p7v-29cm | 4.0: 8.7 | Bypass client_max_size with a base64 multipart part, because read_chunk() kept reading until it had a multiple of four bytes |
CVE-2026-128131 | GHSA-h4cc-hm5h-fmm9 | 4.0: 8.7 | Burn CPU with many concatenated gzip, deflate or zstd members, on a server (request body or WebSocket message) or on a client (response) |
CVE-2026-128132 | GHSA-5rmc-48h2-hvcm | 4.0: 8.7 | Fill memory with WebSocket messages the reader keeps parsing after the receive queue pauses the transport |
CVE-2026-128130 | GHSA-28qf-cpwq-vmc2 | 4.0: 8.3 | Grow the parser buffer and replay already handled requests after a declined upgrade (pure-Python parser only, such as AIOHTTP_NO_EXTENSIONS) |
CVE-2026-128124 | GHSA-jm3w-gw2p-xjfj | 4.0: 8.2 | Stall the loop with a long Host header against an Application.add_domain() mask containing two or more * wildcards |
CVE-2026-128129 | GHSA-pw86-h8fm-j323 | 4.0: 8.2 | Stream unlimited data behind an upgrade request to a handler that does not accept or reject the upgrade right away |
CVE-2026-128128 | GHSA-3rp8-rxj8-mvjw | 3.1: 7.5 | Overflow the C WebSocket reader’s signed 64-bit size check with a frame length near 2^63, so max_msg_size no longer applies |
CVE-2026-128125 | GHSA-5pv8-vvhc-h7jv | 4.0: 6.3 | As a malicious server, make an aiohttp client store an unbounded cookie set and send an oversized Cookie header |
The WebSocket overflow is the simplest of the fixes (commit 8c8906a). reader_py.py is compiled with Cython into the C reader, where _payload_bytes_to_read is a signed 64-bit integer, so adding the buffered length to an attacker-chosen frame length could wrap negative and pass the check:
- projected_size = self._payload_bytes_to_read + len(self._partial)
- if projected_size >= self._max_msg_size:
+ # partial_len declared in reader_c.pxd to keep it in C.
+ partial_len = len(self._partial)
+ # payload_bytes_to_read is a signed 64-bit C value,
+ # use subtraction here to avoid an integer overflow.
+ if self._payload_bytes_to_read >= self._max_msg_size - partial_len:
raise WebSocketError(
WSCloseCode.MESSAGE_TOO_BIG,
Moving the buffered length to the other side of the comparison keeps both operands within range. The concatenated-stream fix (commit d041d4d) caps one call at MAX_DECOMPRESS_MEMBERS = 1024 and decodes members through a window that starts at 64 bytes and doubles, instead of handing each new decompressor the whole remaining buffer. Past the cap, WebSocket readers close with MESSAGE_TOO_BIG. The multipart fix (commit 2d9c5c1) carries partial base64 quartets over to the next chunk rather than reading more data to complete them.
Upgrading to aiohttp 3.14.4 covers all ten CVEs. 3.14.5 (11 October) is the current release. Debian’s packages have no fix yet, so services running the distro python3-aiohttp should install the PyPI wheel in a virtual environment for now:
pip show aiohttp 2>/dev/null | rg '^Version'
rg -n 'aiohttp' requirements*.txt pyproject.toml uv.lock poetry.lock Pipfile.lock 2>/dev/null
dpkg -l python3-aiohttp 2>/dev/null | tail -1
# Handlers exposed to the form, multipart and upgrade paths
rg -n 'await request\.(post|multipart)\(\)|WebSocketResponse\(|add_domain\(' --type py .
TL;DR
This roundup covers application-layer advisories published between 9 and 12 November 2026 that our earlier sweeps had not picked up:
- Apache TomEE 10.3.0 and 11.0.0-M2 (38 CVEs). TomEE posted 38 advisories on 10 November and consolidated them on
oss-securityon 12 November. 26 are fixed in the new releases. The other 12 sit in optional modules (openejb-http,openejb-hessian,openejb-ssh) that were removed outright and will not be patched. The five rated Important: TomEE quietly creates an admin user with a well-known password when the user database is empty (CVE-2026-111257); EJB method authorization is skipped entirely on JDK 21 and later (CVE-2026-86336); MicroProfile JWT role checks on JAX-RS resources are not enforced as declared (CVE-2026-111244); the LDAP identity store accepts empty passwords (CVE-2026-111261); and JAX-WS endpoint constraints only coveredGETandPOST(CVE-2026-111264). Every one of the five credits “Claude Security (tool)” as part of the finding. - MongoDB Node.js driver (
mongodbon npm). Formongodb+srv://strings, the driver checked a normalized SRV host name against the parent domain but then connected to the raw name, in which some characters cut the host short (CVE-2026-126837, CVSS 9.1, versions 3.3.3 up to 7.8.0). Anyone who can tamper with the SRV response can redirect the client, and TLS does not help because the certificate is checked against the redirected name. Separately, 6.7.0 up to 7.9.0 could send OIDC bearer tokens to hosts outsideALLOWED_HOSTS(CVE-2026-126835, fixed in 7.9.0 today). The same 7.8.0 and 6.22.0 releases also closed atimeoutMSconnection pool desync that could return other users’ data (CVE-2026-119179). promzard(npm, unpatched). CERT/CC publishedCVE-2026-127109:promzard4.0.0 and earlier paste the keys of the caller’s context object into a function signature and evaluate it withvm.runInThisContext(). CERT could not reach the maintainers and there is no fixed release.- Python and npm libraries, plus AWS agent tooling. AsyncSSH 2.24.1 fixes an SFTP chroot escape via a
//path prefix (CVE-2026-102643, CVSS 8.8).awslabs.aws-api-mcp-server1.5.1 fixes a deny-list bypass for AWS operations with acronyms in their names (CVE-2026-125271). OpenJD Sessions 0.11.0 / Deadline Cloud worker agent 0.33.0 fixes aPATHhijack that exposed worker AWS credentials (CVE-2026-126087). aiohttp 3.14.4, PapaParse 5.7.1 and Soup Sieve 4.0 fix denial-of-service bugs.
What to do now: Upgrade TomEE to 10.3.0 or 11.0.0-M2 and read the migration guide (several defaults changed). Upgrade mongodb to 7.9.0; there is no 6.x release that fixes the SRV issue. Upgrade asyncssh, aiohttp, papaparse, soupsieve and awslabs.aws-api-mcp-server. Where promzard is in your tree, make sure context keys never come from untrusted input.
Affected packages
| Ecosystem | Package | CVE | Severity | Affected | Fixed |
|---|---|---|---|---|---|
| Maven | org.apache.tomee:tomee-catalina | CVE-2026-111257 | Important | 7.0.0-M1 to before 10.3.0; 11.0.0-M1 (and OpenEJB tomee-catalina 1.5.1 to 1.7.5) | 10.3.0, 11.0.0-M2 |
| Maven | org.apache.tomee:openejb-core | CVE-2026-86336 | Important | 10.1.1 to before 10.3.0; 11.0.0-M1 | 10.3.0, 11.0.0-M2 |
| Maven | org.apache.tomee:mp-jwt | CVE-2026-111244 | Important | 7.1.0 to before 10.3.0; 11.0.0-M1 | 10.3.0, 11.0.0-M2 |
| Maven | org.apache.tomee:tomee-security | CVE-2026-111261 | Important | 8.0.4 to before 10.3.0; 11.0.0-M1 | 10.3.0, 11.0.0-M2 |
| Maven | org.apache.tomee:tomee-webservices | CVE-2026-111264 | Important | 7.0.0-M1 to before 10.3.0; 11.0.0-M1 (and OpenEJB 1.5.0 to 1.7.5, 4.0.0) | 10.3.0, 11.0.0-M2 |
| Maven | TomEE (16 Moderate, 5 Low) | CVE-2026-86811, 87755, 87756, 87758, 97849, 97867, 111240 to 111263 (see list) | Moderate / Low | Before 10.3.0 / 11.0.0-M2 | 10.3.0, 11.0.0-M2 |
| Maven | openejb-http, openejb-hessian, openejb-ssh, openejb-common-cli | CVE-2026-86531, 97870, 97872, 97874, 97880, 97881, 97888, 97890, 111239, 111246, 111250, 111256 | Moderate / Low | All versions | None (modules removed) |
| npm | mongodb | CVE-2026-126837 | CVSS 4.0 9.1 | 3.3.3 to before 7.8.0 | 7.8.0 |
| npm | mongodb | CVE-2026-126835 | CVSS 4.0 5.9 | 6.7.0 to before 7.9.0 | 7.9.0 |
| npm | mongodb | CVE-2026-119179 | CVSS 4.0 8.3 | 6.11.0 to before 6.22.0; 7.0.0 to before 7.8.0 | 6.22.0, 7.8.0 (timeoutMS becomes a no-op) |
| npm | promzard | CVE-2026-127109 | Code injection | <= 4.0.0 | None |
| npm | papaparse | CVE-2026-127056 | CVSS 4.0 8.7 | < 5.7.1 | 5.7.1 |
| PyPI | asyncssh | CVE-2026-102643 | CVSS 3.1 8.8 | < 2.24.1 | 2.24.1 |
| PyPI | awslabs.aws-api-mcp-server | CVE-2026-125271 | CVSS 4.0 8.5 | >= 0.2.13, < 1.5.1 | 1.5.1 |
| PyPI | openjd-sessions / Deadline Cloud worker agent | CVE-2026-126087 | CVSS 4.0 9.4 | < 0.11.0 / < 0.33.0 (Linux, customer-managed fleets) | 0.11.0 / 0.33.0 |
| PyPI | aiohttp | CVE-2026-123817 | CVSS 4.0 8.7 | < 3.14.4 | 3.14.4 |
| PyPI | aiohttp | CVE-2026-128124 to CVE-2026-128132 (nine CVEs, see update) | CVSS 4.0 6.3 to 8.7 | < 3.14.4 | 3.14.4 |
| PyPI | soupsieve | CVE-2026-126190, CVE-2026-126191 | CVSS 3.1 7.5 | < 4.0, < 3.0 | 4.0 |
Technical analysis
1. Apache TomEE: 38 CVEs, five of them Important
TomEE’s security page lists affected Maven artifacts and version ranges for every advisory, and the fixes landed in the apache/tomee repository in October.
Default admin credentials (CVE-2026-111257). With the stock configuration and no users in the default user database, TomEE adds an administrative user with a well-known password at startup. Any web application that uses the default realm and allows “any authenticated user”, or checks the TomEE admin role, can be logged into with those credentials. The affected range starts at tomee-catalina 1.5.1, so this has been present for a long time.
EJB authorization skipped on JDK 21+ (CVE-2026-86336). On JDK 21 and later, openejb-core 10.1.1 to 10.2.x skips EJB method authorization checks entirely, so @RolesAllowed and deployment-descriptor restrictions are not enforced. This one depends on the runtime rather than on configuration, which makes it easy to miss: the same WAR is protected on JDK 17 and open on JDK 21.
JAX-WS endpoints only protected GET and POST (CVE-2026-111264). When TomEE generated a Tomcat context for an EJB web service with authentication configured, it listed only two HTTP methods in the security collection. In Servlet security, a collection that names methods leaves every other method uncovered. The fix (commit ed25e7c03a) drops the method list and denies anything a constraint does not cover:
--- a/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
+++ b/tomee/tomee-webservices/src/main/java/org/apache/tomee/webservices/TomcatWsRegistry.java
- for (final String role : securityRole.split(",")) {
- final SecurityCollection collection = new SecurityCollection();
- collection.addMethod("GET");
- collection.addMethod("POST");
- collection.addPattern("/*");
...
+ static void addSecurityConstraints(final Context context, final String name, final String transportGuarantee) {
+ final String securityRole = SystemInstance.get().getProperty(TOMEE_JAXWS_SECURITY_ROLE_PREFIX + name, "default");
+ for (final String role : securityRole.split(",")) {
+ final SecurityCollection collection = new SecurityCollection();
+ collection.addPattern("/*");
+ collection.setName(role);
...
+ // reject any method a constraint would not cover
+ context.setDenyUncoveredHttpMethods(true);
+ }
The new Javadoc spells out the bug: “a collection without methods covers all verbs, whereas enumerating some (e.g. GET/POST) would leave the others (PUT, DELETE, …) unauthenticated.” SOAP stacks accept requests on methods other than POST more often than people expect, so this is worth testing on any exposed endpoint.
MicroProfile JWT and LDAP (CVE-2026-111244, CVE-2026-111261). In mp-jwt, JAX-RS resources that declared an empty allowed-roles set were open to every caller, subclasses that inherited the same method shared constraints, and class-level constraints on a superclass were ignored. The October commits c89dcc5da3 (“Resolve MP-JWT security constraints per resource class”) and 59698bfe1f (“Apply class-level security annotations of a resource superclass”) match that description. In tomee-security, the Jakarta Security LDAP identity store accepted an empty password whenever the directory allowed unauthenticated binds, which some directories do by default. That is the same LDAP pitfall Traccar fixed this week (CVE-2026-126777).
The Moderate list includes an unauthenticated server shutdown via the admin port (CVE-2026-111251; commit 0fb057efe6 now requires a secret for stop requests), predictable stateful session bean IDs (CVE-2026-87755), path traversal via EJB passivation (CVE-2026-86811), a Derby network service listening on all interfaces (CVE-2026-97849) and database credential disclosure via remote JNDI lookup (CVE-2026-97867).
2. MongoDB Node.js driver: validating one name, connecting to another (CVE-2026-126837)
A mongodb+srv://cluster.example.net string makes the driver look up _mongodb._tcp.cluster.example.net and connect to whatever hosts the SRV records return, as long as they share the parent domain. Before 7.8.0 the driver ran that check on one value and built the connection address from another (commit 19e2d3b83768, src/connection_string.ts):
- for (const { name } of addresses) {
- checkParentDomainMatch(name, lookupAddress);
- }
-
- const hostAddresses = addresses.map(r => HostAddress.fromString(`${r.name}:${r.port ?? 27017}`));
+ const hostAddresses = addresses.map(({ name, port }) => {
+ const host = normalizeDnsName(name);
+ verifySrvHost(host, lookupAddress, options);
+ return HostAddress.fromString(`${host}:${port ?? 27017}`);
+ });
checkParentDomainMatch() looked at the SRV target name, but HostAddress.fromString() parsed the raw r.name as a URL-style host. MongoDB’s advisory says “certain characters end the host name early”, so a target that passes the suffix check can resolve to a different host once it is parsed. TLS does not save you, because the driver then verifies the certificate against that different host name, which the attacker can hold a valid certificate for. An attacker who can forge or modify the SRV response (a compromised resolver, a hostile network, or a cloud DNS misconfiguration) receives the application’s credentials and can return altered query results.
The fix normalizes the name once with normalizeDnsName() (strip the trailing dot, convert to lowercase A-label form) and uses that value for both validation and connection. The same release adds srvAllowedHostsSuffix and srvHostValidator options for teams that want a stricter allow-list. The 7.8.0 release notes state the affected range as “v3.3.3 before v7.8.0” and do not list a 6.x backport.
OIDC bearer token leak (CVE-2026-126835, fixed in 7.9.0). If an application supplied its own OIDC_CALLBACK or OIDC_HUMAN_CALLBACK and the connection string also carried authMechanismProperties=ENVIRONMENT:..., the driver could send the callback’s token to hosts outside the allow-list. Version 7.9.0 refuses the combination outright (commit 9b7f1176dba5):
if (
this.mechanismProperties.ENVIRONMENT &&
(this.mechanismProperties.OIDC_CALLBACK || this.mechanismProperties.OIDC_HUMAN_CALLBACK)
) {
throw new MongoInvalidArgumentError(
`ENVIRONMENT may not be used together with OIDC_CALLBACK or OIDC_HUMAN_CALLBACK for mechanism '${this.mechanism}'.`
);
}
Applications that take connection strings from users (admin consoles, BI tools, data-integration SaaS) are the most exposed, since the user controls authMechanismProperties.
3. promzard: context keys become JavaScript source (CVE-2026-127109, unpatched)
promzard evaluates a template module with a caller-supplied context object. In the current source on GitHub (lib/index.js), the context keys are joined straight into a function parameter list:
const body = `(function(${Object.keys(this.#ctx).join(', ')}) { ${files[this.#file]}\n })`
runInThisContext(body, this.#file).apply(this.#ctx, Object.values(this.#ctx))
Nothing escapes or validates those keys. A key that contains ) and { closes the parameter list early, and whatever follows is compiled as JavaScript and run during evaluation, even if the template file itself is fully trusted. CERT/CC notified the maintainers on 13 October, could not reach them, and published on 12 November. The latest npm release is still 4.0.0 (May 2026).
The library is best known as part of npm init’s prompting stack, where the context comes from local configuration rather than an attacker. The real risk is in other tools that build ctx from parsed config files, HTTP request bodies or environment variables. Until a fix ships, validate that every key matches /^[A-Za-z_$][\w$]*$/ before calling promzard().
4. AsyncSSH, AWS API MCP Server, OpenJD and the DoS fixes
-
AsyncSSH
CVE-2026-102643(commitd4fc430d).SFTPServer.map_path()normalized the client path withposixpath.normpath()and stripped exactly one leading slash. POSIX allowsnormpath()to keep a leading//, so//etc/passwdbecame/etc/passwdafter the strip, andposixpath.join(chroot, "/etc/passwd")discards the chroot because the second argument is absolute. The fix is one line:- return posixpath.join(self._chroot, normpath[1:]) + return posixpath.join(self._chroot, normpath.lstrip(b'/'))Any authenticated SFTP user could read and write anywhere the server’s OS account can.
-
awslabs.aws-api-mcp-serverCVE-2026-125271(commit52bf00157e). The MCP server lets an AI assistant call AWS APIs, with an operator-defined deny-list and elicit-list as the guardrail. Policy entries use kebab-case CLI names, so the server converted botocore operation names with a regex that put a hyphen before every capital letter:- operation_kebab = operation.replace('_', '-') - operation_kebab = re.sub('([A-Z])', r'-\1', operation_kebab).lower().lstrip('-') + operation_kebab = xform_name(operation).replace('_', '-')CreateSAMLProvidercame out ascreate-s-a-m-l-providerand never matched a deny-list entry forcreate-saml-provider. AWS’s advisory names creating federated identity providers, deactivating MFA devices and deleting database clusters as examples of operations that slipped through. Only locally run servers with a custom policy are affected; the hosted offering and theREAD_OPERATIONS_ONLY/REQUIRE_MUTATION_CONSENTsettings are not. -
OpenJD Sessions
CVE-2026-126087. On Linux, the cross-user process launcher inopenjd-sessionsbefore 0.11.0 resolved its helper through aPATHthat a submitted job could change. A user allowed to submit jobs to an AWS Deadline Cloud queue could run code as the worker agent’s OS user and read the AWS credentials it holds. Customer-managed fleets need worker agent 0.33.0; AWS fixed service-managed fleets on its side. -
aiohttp
CVE-2026-123817, PapaParseCVE-2026-127056and Soup SieveCVE-2026-126190/CVE-2026-126191. aiohttp’s WebSocket reader kept onebytesobject per transport read while reassembling a frame, so a peer splitting a frame into tiny reads could use far more memory thanmax_msg_sizesuggests (both servers and clients are affected). PapaParse re-raninput.indexOf(delim, cursor)andinput.indexOf(newline, cursor)on every quoted row even when the last result was still ahead of the cursor, so a single-column quoted CSV with no delimiters took quadratic time; commita50fe19aonly searches again whennextDelim < cursor. Soup Sieve had polynomial work on chained descendant combinators over deep documents (fixed in 4.0) and exponential regex backtracking on digit escapes in selector strings (fixed in 3.0).
Exposure indicators
These are vulnerability disclosures, not malware, so there are no network IOCs. Look for:
- TomEE servers with no users configured in the default user database, TomEE running on JDK 21+, JAX-WS endpoints that answer
PUT/DELETEwithout credentials, or the admin port (8005by default) reachable from other hosts. mongodb+srv://connection strings in applications pinned belowmongodb@7.8.0, and connection strings containingauthMechanismProperties=ENVIRONMENTin apps that also set an OIDC callback.promzard()calls whose context object is built from request bodies, config files or environment variables.- SFTP servers built on
asyncsshwithchrootset, and SFTP logs with paths starting with//.
Detection and remediation
# TomEE version (Maven and on-disk installs)
rg -n '<artifactId>(tomee-[a-z-]+|openejb-[a-z-]+|mp-jwt)</artifactId>' -A1 pom.xml **/pom.xml 2>/dev/null
ls "$CATALINA_HOME"/lib | rg -i 'tomee|openejb' | head
# JAX-WS endpoints that accept methods other than GET/POST without auth (should return 401/403/405)
curl -s -o /dev/null -w '%{http_code}\n' -X PUT https://app.example.internal/webservices/SomeServiceBean
# Node.js: mongodb and promzard versions, direct or transitive
npm ls mongodb promzard papaparse 2>/dev/null
rg -n '"(mongodb|promzard|papaparse)"' package.json package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null
rg -n 'mongodb\+srv://|ENVIRONMENT:' --glob '!node_modules' . 2>/dev/null
# Python
pip show asyncssh aiohttp soupsieve awslabs.aws-api-mcp-server openjd-sessions 2>/dev/null | rg '^(Name|Version)'
rg -n '(asyncssh|aiohttp|soupsieve|aws-api-mcp-server|openjd-sessions)' requirements*.txt pyproject.toml uv.lock poetry.lock 2>/dev/null
- TomEE: upgrade to 10.3.0 or 11.0.0-M2 and follow the migration guide. Before the upgrade, define real users in the default user database (or disable the default realm), block the admin port from the network, and stop using
openejb-http,openejb-hessianand the SSH shell. If you run TomEE on JDK 21+, treat EJB authorization as off until you upgrade. - MongoDB Node.js driver: upgrade to
mongodb@7.9.0. Teams on 6.x have to move to 7.x to get the SRV fix. If you cannot upgrade immediately, switch to amongodb://seed list with explicit hosts, and reject user-supplied connection strings that setENVIRONMENTwhen you also pass an OIDC callback. If DNS was untrusted at any point, rotate the database credentials the application uses. promzard: no patch exists. Validate context keys against a strict identifier pattern, or replace the library where the context is not fully under your control.- Python and npm libraries: upgrade
asyncsshto 2.24.1,aiohttpto 3.14.4,soupsieveto 4.0,papaparseto 5.7.1,awslabs.aws-api-mcp-serverto 1.5.1 and the Deadline Cloud worker agent to 0.33.0. For the AWS API MCP Server, review CloudTrail for operations on your deny-list that ran through the server’s role. For Deadline Cloud, rotate the worker agent’s role credentials if untrusted users can submit jobs.
Timeline
- 2026-08-06 to 2026-08-21:
awslabs/mcpmerges thexform_namefix and releasesaws-api-mcp-server1.5.1 (10 August); OpenJD Sessions 0.11.0 and Deadline Cloud worker agent 0.33.0 ship (20 and 21 August). - 2026-10-04 to 2026-10-13: AsyncSSH 2.24.1 (4 October) and aiohttp 3.14.4 (5 October) are released; Apache TomEE merges fixes for JAX-WS method coverage, MP-JWT constraints, SQL login null passwords, admin-port shutdown and others (7 to 13 October); CERT/CC notifies the
promzardmaintainers (13 October). - 2026-10-29 to 2026-11-03: MongoDB merges NODE-7830 (29 October) and releases Node.js driver 7.8.0 (30 October) and 6.22.0 (2 November); Soup Sieve 4.0 ships (3 November).
- 2026-11-09 to 2026-11-10: NVD publishes
CVE-2026-102643(AsyncSSH) andCVE-2026-123817(aiohttp); AWS publishes bulletins 2026-176-AWS and 2026-177-AWS; Apache TomEE posts 38 advisories on its users list (10 November). - 2026-11-11: PapaParse 5.7.1 is published on npm.
- 2026-11-12: TomEE consolidates the 38 CVEs on
oss-security; NVD publishesCVE-2026-127056(PapaParse),CVE-2026-127109(promzard, CERT/CC VU#685399),CVE-2026-126190/126191(Soup Sieve) andCVE-2026-126837(MongoDB); MongoDB releases Node.js driver 7.9.0 with theCVE-2026-126835fix. - 2026-11-13: NVD publishes nine more aiohttp 3.14.4 CVEs (
CVE-2026-128124toCVE-2026-128132), five days after aio-libs posted the matching GitHub advisories on 8 November. Debian tracks them in bug1153954.
From research to remediation
Check whether this pattern exists in your codebase
Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.
References
- Apache TomEE security page: vulnerabilities fixed in 10.3.0 and 11.0.0-M2 (38 CVEs)
- oss-security (12 November 2026): Apache TomEE: 38 CVEs addressed in 10.3.0 and 11.0.0-M2
- Apache TomEE commit ed25e7c03a: protect all HTTP methods on JAX-WS endpoint security constraint (CVE-2026-111264)
- MongoDB Node.js driver v7.8.0 release notes (CVE-2026-126837 and CVE-2026-119179) and commit 19e2d3b83768 (NODE-7830)
- MongoDB Node.js driver v7.9.0 release notes (CVE-2026-126835)
- MongoDB JIRA NODE-7830: Configurable DNS / SRV host normalization
- CERT/CC Vulnerability Note VU#685399: promzard code injection (CVE-2026-127109)
- AsyncSSH GHSA-w29m-45fc-22v9 and commit d4fc430d (CVE-2026-102643)
- awslabs/mcp GHSA-4wq9-grf3-qg2p and AWS Security Bulletin 2026-176-AWS (CVE-2026-125271)
- AWS Security Bulletin 2026-177-AWS: OpenJD Sessions / Deadline Cloud worker agent (CVE-2026-126087)
- aiohttp GHSA-2g87-pp6c-29x5 (CVE-2026-123817), PapaParse commit a50fe19a (CVE-2026-127056), and Soup Sieve GHSA-mmhr-3c5m-f64f / GHSA-6655-6qjp-jx7x
- aiohttp 3.14.4 release and advisories GHSA-3rp8-rxj8-mvjw, GHSA-24c4-3p7v-29cm, GHSA-h4cc-hm5h-fmm9 and six others (CVE-2026-128124 to CVE-2026-128132)
- aiohttp commit 8c8906a: fix oversized frames on WebSocket messages (CVE-2026-128128)
- Debian security tracker: CVE-2026-128128 (python-aiohttp, bug 1153954)