65
CVEs
11
Critical
33
High
0
KEV
0
PoC
18
Unpatched C/H
63.1%
Patch Rate
0.3%
Avg EPSS
Severity Breakdown
CRITICAL
11
HIGH
33
MEDIUM
21
LOW
0
Monthly CVE Trend
Affected Products (30)
Eclipse Theia
9
Eclipse Jetty
8
Eclipse Milo
6
Java
4
Eclipse Glassfish
4
Eclipse Aerios
3
Eclipse Csi Pia
3
Eclipse Openj9
2
Eclipse Basyx
2
Openj9
2
Tomcat
2
Eclipse Ditto
2
Eclipse Open Vsx
2
Eclipse Vert X
2
Eclipse Ankaios
2
Eclipse Arrowhead
2
Eclipse Kuksa Databroker
2
Ssti
1
Eclipse Mojarra
1
Python
1
Eclipse Sw360
1
Eclipse Rdf4J
1
Eclipse Threadx Netx Duo
1
Eclipse Omr
1
Eclipse Basyx Java Server Sdk
1
Eclipse Kura
1
Docker
1
Eclipse Basyx Go Components
1
Kubernetes
1
Eclipse Lyo
1
Top Risky CVEs
| CVE | Summary | Severity | CVSS | EPSS | Priority | Signals |
|---|---|---|---|---|---|---|
| CVE-2026-7411 | Remote code execution in Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10 allows unauthenticated remote attackers to write arbitrary files anywhere on the host filesystem via path traversal in the Submodel HTTP API's file upload fileName parameter, leading to complete system compromise. The vulnerability receives the maximum CVSS score of 10.0 due to network-accessible exploitation requiring no authentication, privileges, or user interaction, with scope change enabling impact beyond the vulnerable component. EPSS data not available; KEV status not confirmed; exploitation status depends on release recency and deployment exposure of this industrial automation SDK. | CRITICAL | 10.0 | 0.1% | 50 |
|
| CVE-2026-15704 | We need to produce a JSON object with specific fields based on all provided data. The key is to synthesize from multiple sources: CVE description, CVSS vector, CWE, EPSS, patch availability, CPE, tags, SSVC, references, EUVD, source code diff. The analysis should be comprehensive. Let's extract and synthesize. Product name: "Eclipse BaSyx Go Components" (3 words: Eclipse BaSyx Go Components, but "Eclipse BaSyx Go Components" is the exact product; "Eclipse BaSyx" might be too generic. "Eclipse BaSyx Go" is 3 words. However, the description says "Eclipse BaSyx Go Components", CPE: eclipse_foundation:eclipse_basyx_go_components. Could be "Eclipse BaSyx Go Components" but that's 4 words. Perhaps "BaSyx Go Components" or "Eclipse BaSyx". The requirement: "1-3 words ONLY. The specific product or service name affected." So "Eclipse BaSyx Go" could be 3 words. Actually "Eclipse BaSyx Go" is three. But the official product might be "Eclipse BaSyx" (the project) but the component is "Go Components". I'll use "Eclipse BaSyx Go" as the product. Now summary: need a 2-3 sentence plain-language summary. Do not copy description. Start with specific impact verb and product. For example: "Authorization bypass in Eclipse BaSyx Go Components ABAC deployments allows unauthenticated remote attackers to access protected API routes by appending trailing slashes." Should mention what the vulnerability is, who affected, what attacker can do. Mention if actively exploited (KEV status: no KEV mentioned, so "no public exploit identified at time of analysis" or "publicly available exploit code exists"? SSVC says Exploitation: poc. So a POC exists. So it's "publicly available exploit code exists". Also EPSS 0.35% low. So summary: "Authorization bypass in Eclipse BaSyx Go Components v1.0.0 and earlier allows unauthenticated remote attackers to bypass Attribute-Based Access Control (ABAC) by appending a trailing slash to API requests, leading to unauthorized read, write, or delete operations on | CRITICAL | 9.8 | 0.4% | 49 |
|
| CVE-2026-12605 | Server-Side Request Forgery combined with CSRF in Eclipse GlassFish's DownloadServlet ContentSources handler allows a remote attacker to exfiltrate the administrative `gfresttoken` to an attacker-controlled host when an authenticated administrator visits a malicious page. Affecting Eclipse GlassFish 8.0.x prior to 8.0.4, successful token theft yields full control of the GlassFish administrative domain until the token expires, effectively an unauthenticated takeover of the management plane. No public exploit identified at time of analysis, and the issue is not in CISA KEV, but the CVSS 9.6 rating and low attack complexity make it high priority. | CRITICAL | 9.6 | 0.2% | 48 |
|
| CVE-2026-2587 | Remote code execution in Eclipse GlassFish allows remote attackers to evaluate arbitrary Expression Language (EL) expressions through the gadget handler's server-side template rendering of .xml files, leading to full host compromise. The vulnerability (CVSS 9.6, CWE-917) requires user interaction but no authentication, and is demonstrable by submitting payloads like #{7*7} which the server evaluates to 49. No public exploit identified at time of analysis and the issue is not listed in CISA KEV. | CRITICAL | 9.6 | 0.2% | 48 |
|
| CVE-2026-82180 | Authentication bypass in Eclipse Arrowhead 5.0.0 through 5.2.1 lets an unauthenticated attacker who can publish to the MQTT broker impersonate the cloud's system operator. When the MQTT API runs with the certificate authentication policy, CertificateMqttFilter reads an X.509 certificate straight from the MQTT message payload and trusts its Subject DN without ever verifying the signature or issuer chain, reducing authorization to two string comparisons on public, attacker-controlled values. By minting a self-signed certificate with CN=Sysop.<cloud>.<org>.arrowhead.eu and dnQualifier=op, the attacker gains isSysOp==true and full management access. No public exploit is identified at time of analysis, but the technique is described in full detail in the advisory. | CRITICAL | 9.5 | 0.2% | 48 |
No patch
|
| CVE-2026-60007 | Password recovery in Eclipse Milo (the open-source OPC UA SDK for Java) versions 0.6.0 through 1.1.4 allows an on-path attacker to break username-token confidentiality via a Bleichenbacher-style padding oracle. The server returns distinguishable error responses for invalid RSA PKCS#1 v1.5 padding versus other authentication failures during username-token processing, so an attacker who captures a victim's Basic128Rsa15-encrypted username token can send repeated unauthenticated ActivateSession requests to recover the cleartext password and then authenticate as the victim. No public exploit identified at time of analysis and it is not listed in CISA KEV; the weakness and its upstream fix are confirmed by the Eclipse Foundation. | CRITICAL | 9.1 | 0.5% | 46 |
No patch
|
| CVE-2026-18918 | Authorization bypass in Eclipse Lyo 2.0.0 through 7.0.0 lets remote attackers abuse the 2-legged OAuth flow to promote a self-registered 'provisional' trusted client into a fully trusted one without the required administrator approval. Applications that build their authorization filters on Lyo's AbstractAdapterCredentialsFilter are affected, allowing an attacker to act as a trusted OAuth client and access protected OSLC resources. No public exploit identified at time of analysis, and it is not listed in CISA KEV; fixes shipped in 6.0.1.Final and 7.0.0.Beta3. | CRITICAL | 9.1 | 0.4% | 46 |
|
| CVE-2026-2586 | Remote code execution in Eclipse GlassFish allows attackers with administrative access to the Administration Console to execute arbitrary operating system commands as the application service user. The flaw stems from improper input handling in admin panel requests (CWE-94), and while CVSS rates it 9.1 due to scope change and full CIA impact, exploitation requires high privileges (PR:H). No public exploit identified at time of analysis and the issue is not listed in CISA KEV. | CRITICAL | 9.1 | 0.2% | 46 |
|
| CVE-2026-2332 | HTTP request smuggling in Eclipse Jetty's HTTP/1.1 parser lets remote unauthenticated attackers desynchronize front-end/back-end request boundaries by abusing quoted-string chunk extensions. Jetty incorrectly terminates chunk-extension parsing at a CRLF located inside an unterminated quoted-string (e.g. `1;a="`) rather than rejecting it, so attacker-controlled bytes are reinterpreted as a second, smuggled request on the same TCP connection. Publicly available exploit code exists (a working Python PoC ships in the GHSA advisory), though EPSS is very low (0.03%, 9th percentile) and the issue is not on CISA KEV. | CRITICAL | 9.1 | 0.0% | 46 |
|
| CVE-2026-82955 | Improper certificate validation in the KrakenD-based API Gateway of Eclipse aeriOS allows a network man-in-the-middle to compromise bearer-token validation. The bundled KrakenD configuration hard-codes disable_jwk_security to true with no Helm override, so KrakenD skips TLS certificate verification (and in the shipped config fetched the JWKS over plaintext HTTP) when retrieving the JSON Web Key Set used to validate JWTs. Only pre-release development builds are affected; there is no public exploit identified at time of analysis and the flaw is not in CISA KEV. | CRITICAL | 9.0 | 0.1% | 45 |
No patch
|
| CVE-2026-57898 | Unauthenticated arbitrary file write in Eclipse BaSyx Java Server SDK (2.0.0-milestone-05 through 2.0.0-milestone-12) lets remote attackers plant files anywhere the Java process can write when the server is deployed with the MongoDB file backend, potentially escalating to remote code execution. The AAS thumbnail API trusts a client-supplied fileName that is later reused as a filesystem path, so a traversal or absolute-path filename lands attacker-controlled bytes outside the intended directory. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, but the vendor-fixed release (2.0.0-milestone-13) is available. | CRITICAL | 9.0 | 0.4% | 45 |
|
| CVE-2026-80515 | Authorization bypass in Eclipse Arrowhead 5.0.0-5.2.1 allows any authenticated system - regardless of privilege level - to reach every protected management API endpoint by submitting percent-encoded paths that defeat the raw-URL substring check while still being routed by Spring MVC's decoded dispatcher. Exploiting the flaw is trivial: encoding a single character in '/mgmt/' (e.g. 'm' → '%6D') causes the filter to fall through without authorizing the request, yet Tomcat decodes and dispatches it normally. The highest-impact target is POST /authentication/mgmt/identities, which creates new sysop-level accounts, yielding full administrative takeover of the Arrowhead local cloud. No public exploit has been identified at time of analysis. | HIGH | 8.9 | 0.3% | 44 |
No patch
|
| CVE-2026-82217 | Path traversal in Eclipse Theia 1.73.0-1.74.x AI Agent Mode allows arbitrary file writes outside the workspace with backend OS user privileges through model-supplied paths that bypass workspace-containment checks. The affected tools - writeFileContent, suggestFileContent, and associated replacement and state helpers - accept relative paths such as ../.bashrc, absolute paths, or tilde-expanded paths like ~/.ssh/authorized_keys without boundary validation. Because path arguments derive from LLM output, an indirect prompt injection attack embedded in developer-loaded content can steer writes to host-executed files and escalate to backend code execution; Agent Mode applies writes silently with no confirmation dialog. No public exploit code or CISA KEV listing exists at time of analysis, though the prompt-injection attack surface is realistic in cloud IDE deployments. | HIGH | 8.8 | 0.4% | 44 |
|
| CVE-2026-58080 | Silent authorization bypass in Eclipse Milo OPC UA server SDK versions 1.0.0-1.1.4 allows anonymous network clients to invoke protected methods, read role-permission metadata, and delete protected nodes. The defect is a missing field copy in `OpcUaServerConfig.copy()`: when servers construct their running configuration via this method, the configured `RoleMapper` is silently dropped, causing the `DefaultAccessController` to receive empty role ID lists for every session and skip all role-permission enforcement. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV. | HIGH | 8.8 | 0.4% | 44 |
|
| CVE-2026-18353 | Server-side request forgery in the Eclipse CSI PIA `POST /v1/upload/sbom` endpoint lets remote attackers coerce the server into connecting to an arbitrary host, port, and scheme of their choosing. By exploiting a parser-differential between Python's `urlparse` (used for the issuer allowlist check) and `requests`/`urllib3`/`urllib` (used for OIDC discovery and JWKS retrieval), an attacker crafts a JWT `iss` claim containing a backslash that passes validation but resolves to a different host during the actual fetch. The `iss` claim is only checked in its unverified form, so no legitimate token is needed; no public exploit has been identified at time of analysis and the issue is not listed in CISA KEV. | HIGH | 8.8 | 0.2% | 44 |
|