Skip to content
Applications

CVE-2026-84736

8.3
High
EPSS 0.17%Patch availableSep 4, 2026

Federator disables TLS validation by default, enabling MITM theft of OAuth tokens.

common questions

Is CVE-2026-84736 being exploited?

Not confirmed. CVE-2026-84736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.

How severe is CVE-2026-84736?

CVE-2026-84736 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84736?

Yes. A fix has been recorded for CVE-2026-84736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84736 affect?

CVE-2026-84736 affects Eclipse aeriOS Federator (development builds), Helm chart and Docker Compose defaults prior to fix. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84736?

Update to fixed Helm/Docker release, set TLS_CERTIFICATE_VALIDATION=true, rotate exposed tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Eclipse aeriOS Federator (development builds)Helm chart and Docker Compose defaults prior to fix
impact

MITM attackers can impersonate external services to steal OAuth client credentials and bearer tokens, exposing sensitive data.

action required

Immediate action required

affected versions
Eclipse Foundation Eclipse aeriOS
  • affected>= d730017a4a0e2a31feba6258bd780efbce7e0d5d and < 9c63b60becc9873b0195ff9cd6582b69cb12d4f2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free