p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in eclipse

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für eclipse: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 10

  1. CVE-2026-22551

    Mittel · CVSS 6.7EPSS 0,31%Keine Korrektur veröffentlicht

    CVE-2026-22551

    In Eclipse Theia versions prior to 1.71.0, the AI chat rendered Markdown image tags from AI responses, triggering HTTP requests to arbitrary external URLs without restriction. Combined with prompt injection in a malicious workspace, an attacker could induce the AI agent to construct image URLs encoding sensitive information from the workspace or conversation context, exfiltrating it to attacker-controlled servers. The workspace trust enforcement introduced in v1.71.0 mitigates the documented attack chain by disabling AI features in untrusted workspaces.

    Veröffentlicht Aktualisiert
  2. CVE-2026-46580

    Hoch · CVSS 8.4EPSS 0,51%Keine Korrektur veröffentlicht

    CVE-2026-46580

    In Eclipse Theia versions prior to 1.71.0, files matching the pattern .prompts/*.prompttemplate in a workspace were automatically loaded and could override or extend the AI agent's system prompts. An attacker could craft a malicious repository containing prompt template files that, when the workspace was opened in Theia, replaced the AI's system instructions with attacker-controlled content (indirect prompt injection). Combined with other AI chat features available in untrusted workspaces, this enabled attack chains leading to data exfiltration via Markdown image rendering or arbitrary command execution via task definitions.

    Veröffentlicht Aktualisiert
  3. CVE-2026-7412

    Hoch · CVSS 8.6EPSS 0,52%Keine Korrektur veröffentlicht

    CVE-2026-7412

    In Eclipse BaSyx Java Server SDK versions prior to 2.0.0-milestone-10, the Operation Delegation feature fails to validate the destination URI of delegated requests. An unauthenticated remote attacker can exploit this design flaw to force the BaSyx server to execute blind HTTP POST requests to arbitrary internal or external targets. This allows an attacker to bypass network segmentation and pivot into isolated internal IT/OT infrastructure or target Cloud Metadata services (IMDS).

    Veröffentlicht Aktualisiert
  4. CVE-2023-6194

    Niedrig · CVSS 2.8EPSS 0,32%Keine Korrektur veröffentlicht

    CVE-2023-6194

    In Eclipse Memory Analyzer versions 0.7 to 1.14.0, report definition XML files are not filtered to prohibit document type definition (DTD) references to external entities. This means that if a user chooses to use a malicious report definition XML file containing an external entity reference to generate a report then Eclipse Memory Analyzer may access external files or URLs defined via a DTD in the report definition.

    Veröffentlicht Aktualisiert
  5. CVE-2023-4218

    Mittel · CVSS 5EPSS 0,39%Keine Korrektur veröffentlicht

    XXE in eclipse.platform / Eclipse IDE

    In Eclipse IDE versions < 2023-09 (4.29) some files with xml content are parsed vulnerable against all sorts of XXE attacks. The user just needs to open any evil project or update an open project with a vulnerable file (for example for review a foreign repository or patch).

    Veröffentlicht Aktualisiert
  6. CVE-2020-27225

    Hoch · CVSS 7.8EPSS 0,34%Keine Korrektur veröffentlicht

    CVE-2020-27225

    In versions 4.18 and earlier of the Eclipse Platform, the Help Subsystem does not authenticate active help requests to the local help web server, allowing an unauthenticated local attacker to issue active help commands to the associated Eclipse Platform process or Eclipse Rich Client Platform process.

    Veröffentlicht Aktualisiert
  7. CVE-2020-27218

    Mittel · CVSS 4.8EPSS 8,28%Keine Korrektur veröffentlicht

    CVE-2020-27218

    In Eclipse Jetty version 9.4.0.RC0 to 9.4.34.v20201102, 10.0.0.alpha0 to 10.0.0.beta2, and 11.0.0.alpha0 to 11.0.0.beta2, if GZIP request body inflation is enabled and requests from different clients are multiplexed onto a single connection, and if an attacker can send a request with a body that is received entirely but not consumed by the application, then a subsequent request on the same connection will see that body prepended to its body. The attacker will not see any data but may inject data into the body of the subsequent request.

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →