CVE-2026-84736: High severity Eclipse aeriOS vulnerability

Published Sep 3, 2026
·
Updated

In the current development version of Eclipse aeriOS, for which no official release has yet been published, the Federator component disables TLS certificate validation for outbound HTTPS connections by default. When the TLSCERTIFICATEVALIDATION environment variable is unset or set to false, the component configures its HTTP transport to skip TLS certificate verification.

As a result, an attacker able to intercept network communications between the Federator and external services could impersonate those services and intercept sensitive information transmitted over HTTPS, including OAuth client credentials and bearer tokens.

The issue has been addressed by enabling TLS certificate validation by default. The TLSCERTIFICATEVALIDATION environment variable is now set to true in the default configuration provided by the Helm chart and Docker Compose deployment.

Affected Software

1 affected component
Eclipse aeriOS=current development version

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In the Helm chart and Docker Compose deployment, set the TLS_CERTIFICATE_VALIDATION environment variable to true so the Federator enables TLS certificate validation for outbound HTTPS connections.

    Eclipse aeriOS Federator TLS_CERTIFICATE_VALIDATION = true
  2. Configuration

    Ensure TLS_CERTIFICATE_VALIDATION is not unset and not set to false; otherwise the Federator will configure its HTTP transport to skip TLS certificate verification.

    Eclipse aeriOS Federator TLS_CERTIFICATE_VALIDATION = not unset/false

Event History

Sep 3, 2026
CVE Published
via MITRE·04:10 PM
Data Sourced
via MITRE·04:10 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments of the Federator component are exposed when they make outbound HTTPS connections with TLS_CERTIFICATE_VALIDATION unset or set to false. Exploitation requires an attacker to be able to intercept communications between Federator and the external service.

2

Are default deployments affected?

The vulnerable behavior was the default when TLS_CERTIFICATE_VALIDATION was unset. The corrected Helm chart and Docker Compose default configuration set TLS_CERTIFICATE_VALIDATION to true.

3

What can be done if the updated deployment configuration cannot be applied immediately?

Set TLS_CERTIFICATE_VALIDATION to true explicitly for the Federator component. This causes its HTTP transport to verify TLS certificates for outbound HTTPS connections.

4

How can I determine whether my deployment is affected?

Check the Federator environment configuration for TLS_CERTIFICATE_VALIDATION. It is affected if the variable is absent or explicitly set to false.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203