In the current development version of Eclipse aeriOS, which has not yet had an official release, the KrakenD instance included in the API Gateway component had the disable_jwk_security parameter hard-coded to true, with no option to override it through the Helm chart configuration. This setting disables TLS certificate verification when KrakenD retrieves the JSON Web Key Set (JWKS) used to validate bearer tokens, potentially allowing an attacker with the ability to intercept this communication to provide a malicious JWKS and compromise token validation.
The issue has been addressed by making the parameter configurable through the boolean Helm value krakend.config.disableJwkSecurity and setting its default value to false, ensuring that TLS certificate verification is enabled by default.
In Eclipse Ditto versions [1.3.0, 3.9.6], the ImplicitThingCreationMessageMapper of the connectivity service builds a CreateThing command by substituting placeholder values (e.g. {{ header:device_id }}) resolved from inbound message headers into a pre-configured JSON "thing" template as raw, un-escaped strings, and then parses the resulting string as JSON. Because the placeholder engine performs no JSON escaping and is unaware of the surrounding JSON string context, a resolved value containing a double-quote character can break out of its string and inject additional JSON structure.
When a connection is configured to use this mapper with a template that reflects a header whose value a publishing device can control (for example an MQTT 5 user property, an AMQP 1.0 application property, or a Kafka record header), an attacker able to publish on that connection can inject an inline _policy object. The inline policy overrides the administrator-configured policyId, letting the attacker assign an arbitrary access-control policy to the newly created digital twin — gaining full read/write access to it and potentially revoking the legitimate owner's access, with no administrator interaction.
Exploitation requires all of the following: the connection uses the (non-default) ImplicitThingCreation mapper; its template reflects an attacker-controllable header; and, for the policy-override impact, the connection's authorization subjects are permitted to create policies (the default). Deployments that restrict the connection's subjects to thing creation only via the entity-creation configuration are not affected by the policy-override impact.
In Eclipse Ditto versions 3.0.0 to 3.9.6, the Things service fetches WoT (Web of Things) ThingModels over HTTP from URLs supplied by API users in the definition field of a Thing or Feature, without validating the target host, and follows HTTP redirects without re-validating the redirect target and without a hop limit. An authenticated user who is permitted to create a Thing, or who holds WRITE permission on an existing Thing, can thereby cause the Things service to issue arbitrary HTTP GET requests from inside the deployment's network — including to cloud instance-metadata endpoints and other internal services — and can use the differing error responses returned to the caller to enumerate internal services. Versions 2.4.0 to 2.5.x contain the same code, but are only affected where the operator explicitly enabled the WoT integration feature toggle, which is disabled by default in those versions.
Eclipse Theia versions 1.73.0 up to but not including 1.75.0 contain a path traversal vulnerability in the AI Agent Mode file-change tools. This flaw allows crafted file paths to write or delete files outside the workspace without proper containment checks. Exploitation can lead to arbitrary file modification with the privileges of the Theia backend OS user, potentially enabling code execution on the host system.
Eclipse Lyo versions 2.0.0 to 7.0.0 contain a vulnerability where OAuth server authorization checks can be bypassed when 2-legged authentication is supported by the server. Applications using the Lyo-provided AbstractAdapterCredentialsFilter for authorization filtering are vulnerable. An attacker can create a provisional trusted client and immediately use it as a trusted client without administrator approval. The 3-legged OAuth path requiring user interaction is not affected. This vulnerability has a critical severity with a CVSS score of 9.1.
CVE-2026-79653 is a path traversal vulnerability in Eclipse SW360 versions 19.0.0, 19.1.0, 19.2.0, 20.0.0, and 20.1.0 when configured to use file system storage via the enable.attachment.store.to.file.system setting. An attacker can manipulate uploaded filenames to traverse directories arbitrarily. The vulnerability can be mitigated by disabling this configuration or updating to fixed versions.
Eclipse OpenJ9 versions up to 0.60 contain a vulnerability where a crafted .class file with deeply nested annotations can cause a segmentation fault due to uncontrolled recursion. This issue is identified as CWE-674. The vulnerability has a medium severity with a CVSS score of 5.7.
In Eclipse Theia versions up to and including 1.69.0, opening a folder starts source control integration without requiring the user to trust the folder first. This affects applications built on Theia that include the git integration, such as the Theia IDE. Both Theia's own `@theia/git` extension and the builtin VS Code `git` extension run git commands such as `git status` as soon as a repository is detected. Since git honors repository-local configuration, a folder containing an attacker-controlled `.git/config` with `core.fsmonitor` (or a comparable hook-like setting) causes the configured command to be executed. The configuration can be delivered by burying a bare repository inside a regular repository (OVE-20210718-0001), so cloning an attacker-supplied repository and opening it in a Theia-based application is sufficient to execute arbitrary commands with the privileges of the user, without any confirmation prompt.
As of 1.70.0, plugins that declare `capabilities.untrustedWorkspaces.supported: false`, which includes the builtin git extension, are no longer loaded or activated in an untrusted workspace, and the deprecated `@theia/git` extension has been removed, so no git command is executed against an untrusted folder.
In Eclipse RDF4J, several XML parser entry points do not fully restrict XML External Entity (XXE) processing when parsing untrusted XML-based RDF data or query results, permitting DOCTYPE declarations, external entity references, and external DTD loading. This is due to an incomplete fix for CVE-2018-1000644: the earlier fix did not cover all parser entry points. The issue is resolved in RDF4J 5.3.2, which rejects or disables DOCTYPE declarations, external entities, and external DTD loading by default.
CVE-2026-12605 is a critical vulnerability in Eclipse GlassFish versions 8.0.0 before 8.0.4. It involves a combination of CSRF and SSRF vulnerabilities in the DownloadServlet ContentSources that can leak the admin gfresttoken to an attacker-controlled host if the victim is authenticated in the Admin Console. This leakage allows an unauthenticated attacker to fully take over the Eclipse GlassFish domain until the token expires.
CVE-2026-46581 is a high severity path traversal vulnerability in Eclipse Mojarra version 2.3. The issue arises from improper URL handling in the DefaultFaceletFactory component, which fails to sanitize or block remote URLs. This flaw allows an attacker to specify a remote Facelet URL that the server includes and processes with its privileges, potentially exposing restricted files such as WEB-INF/web.xml or /etc/passwd.
Eclipse Theia versions up to and including 1.73.1 contain a directory traversal vulnerability in the @theia/filesystem backend HTTP file-download endpoints. These endpoints convert client-supplied URIs directly to filesystem paths without restricting access to the workspace or allowed roots. In browser deployments, token enforcement is ineffective on HTTP requests, allowing unauthenticated clients to read any file accessible by the backend process, including sensitive files outside the workspace. Electron mode is not affected by this vulnerability via this path.
Eclipse Theia versions up to and including 1.73.1 have a vulnerability in the @theia/filesystem backend where an unauthenticated attacker can perform arbitrary file writes outside the workspace via a specially crafted POST /file-upload request. This occurs because the handler accepts an absolute path from user input without workspace confinement or authentication. Browser deployments are affected due to insufficient token enforcement on HTTP requests, enabling cross-origin web pages to exploit this without credentials. Electron mode is not affected by this issue. The vulnerability has a high severity CVSS score of 8.8 and can lead to remote code execution by overwriting critical files such as ~/.bashrc.
Eclipse Theia versions 1.66.0 through 1.73.1 contain a directory traversal vulnerability in the @theia/plugin-ext backend. The HTTP endpoint /hostedPlugin/:pluginId/:path(*) improperly resolves file paths without verifying that the resolved path remains within the plugin directory. This allows unauthenticated network attackers to retrieve arbitrary files readable by the Theia backend process by sending encoded traversal sequences. Plugin IDs are deterministic, enabling attackers to target built-in plugins without prior system knowledge. The vulnerability has a high severity with a CVSS score of 7.5.
Eclipse Theia versions 0.7.0 through 1.73.1 contain a vulnerability in the PreferenceUtils.merge function that allows prototype pollution via crafted preference values in workspace settings files. This occurs because the merge function does not reject prototype-related keys, potentially altering application logic when a workspace is opened.
An XML External Entity (XXE) vulnerability (CWE-611) exists in Eclipse Accessibility Tools Framework (ACTF) versions up to 1.6.0, including source versions up to v20260630 and miChecker up to 3.1.0. Exploitation could allow a malicious actor to access local or internal network resources on systems running affected applications. The vulnerability has a medium severity with a CVSS 4.6 score. No official patch or remediation guidance has been provided yet.
Eclipse Milo versions 0.6.0 through 1.1.4 have a vulnerability where OPC UA server diagnostics nodes do not enforce access authorization. This allows an anonymous client to enable diagnostics without authentication and a trusted client to read sensitive security diagnostics of other sessions, including usernames and authentication details.