Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-47097 – Information Disclosure via Hardcoded AES Key – AJA HELO Plus < 2.1.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-47097 is a high-severity information disclosure vulnerability in AJA HELO Plus firmware. The device relies on a static AES passphrase embedded in obfuscated form within the firmware image to protect diagnostics export bundles served from an unauthenticated diagnostics endpoint, allowing anyone who recovers the passphrase from the firmware to decrypt sensitive diagnostics data from any affected device. The issue carries a CVSS v4.0 base score of 8.7 (High) and requires no authentication or user interaction to exploit remotely.

Technical details

  • Root cause: HELO Plus firmware prior to version 2.1.7 encrypts exported diagnostics bundles using a static, hardcoded AES passphrase (CWE-321: Use of Hard-coded Cryptographic Key). The passphrase is obfuscated within the firmware rather than being unique per device or user-supplied.
  • Trigger conditions: An attacker obtains the publicly available HELO Plus firmware image and reverse engineers it to recover the embedded AES passphrase. Because the same passphrase is shared across all affected units, it can be reused against any vulnerable device.
  • Attack vector: The device exposes an unauthenticated diagnostics endpoint (/diags) from which the encrypted diagnostics export bundle can be retrieved over the network without credentials. Once the attacker has the shared passphrase, the retrieved bundle can be decrypted offline.
  • Impact: Successful exploitation discloses the contents of the diagnostics bundle, described by the vulnerability record as "highly sensitive server information." The vulnerability affects confidentiality only — it does not impact integrity or availability.

Affected software

  • AJA HELO Plus firmware versions prior to 2.1.7 (all versions before 2.1.7 are affected)
  • Fixed in AJA HELO Plus firmware version 2.1.7

Severity

  • CVSS v4.0 Base Score: 8.7 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade all AJA HELO Plus units to firmware version 2.1.7 or later. This release changes the diagnostics export workflow so that the downloaded diagnostic archive is encrypted using a passphrase supplied by the user at export time, rather than a static value embedded in the firmware.
  • If patching cannot be performed immediately: Restrict network access to the HELO Plus management/diagnostics interface to trusted management networks only, and avoid exposing the device’s web/diagnostics interface directly to the internet, until the firmware update can be applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge