On this page

Atomicorp WAF Research Note: CVE-2026-84175

Eclipse Ditto Uncontrolled Recursion Vulnerability

CVE Details

Status: Attack Blocked by Atomicorp
  • Already protected by existing Atomicorp WAF rules
  • Protection status: Understanding Atomicorp WAF Protection Status
  • CVE: CVE-2026-84175
  • Name: Eclipse Ditto Uncontrolled Recursion Vulnerability
  • Severity: Medium
  • CVSS: 5.3 (v4.0) (Medium)
  • CVSS version: 4.0
  • CVSS source: eclipse CNA
  • CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
    • Attack vector: Network
    • Attack complexity: Low
    • Attack requirements: None
    • Privileges required: Low
    • User interaction: None
    • Vulnerable-system confidentiality: Low
    • Vulnerable-system integrity: None
    • Vulnerable-system availability: Low
    • Subsequent-system confidentiality: Low
    • Subsequent-system integrity: None
    • Subsequent-system availability: None
    • Scope: X
  • CWE: CWE-674 — Uncontrolled Recursion, CWE-918 — Server-Side Request Forgery (SSRF)
  • Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-230 , CAPEC-231 , CAPEC-664
  • Vendor: Eclipse Foundation
  • Vulnerable product: Eclipse Ditto
  • CVE published: 2026-09-02
  • CVE last modified: 2026-09-03
  • EPSS: 0.0029; 21.4th percentile (FIRST )
  • Latest Update: 2026-09-06
  • Selected Rule IDs observed: 337109 , 337110 , 344360 , 398001 , 398021 , 398022
  • Matching rules: 6; rules with blocking actions: 5
  • Would-block Rule IDs: 337109 , 337110 , 344360 , 398021 , 398022
  • Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request cookies, SOAP request data, XML request data

Vulnerability Description

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.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (337109 , 337110 , 344360 , 398001 , 398021 , 398022 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: Eclipse Foundation Eclipse Ditto versions through 3.9.6.
    • Affected versions: Eclipse Foundation Eclipse Ditto versions through 3.8.12.
    • Affected versions: Eclipse Foundation Eclipse Ditto versions earlier than 3.0.0.
    • Recommended upgrade: Upgrade Eclipse Foundation Eclipse Ditto to 3.0.0 or later.

  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

  • Source: Atomicorp AI Research Framework
  • Tags: cve, derived, ssrf, waf-probe

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ .