Improper physical side-channel protection in Microchip AN1044, AN953, and SW300052

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-89172?

CVE-2026-89172 is a vulnerability classified as Improper Protection of Physical Side Channels, affecting AN1044 (affected versions: ≤ A), AN953 (affected versions: ≤ A), and SW300052 (affected versions: ≤ 2.6). This vulnerability is rated Medium, with a CVSS score of 5.6. There is not enough data to determine whether this vulnerability has been exploited.

Overview

Original source data

Improper protection of physical side channels vulnerability in Microchip AN1044, Microchip AN953, and Microchip SW300052. This issue affects AN1044: through A; AN953: through A; SW300052: through 2.6.

Affected products and scope

  • Microchip AN1044: versions from 0 through and including A are marked affected by the normalized record.
  • Microchip AN953: versions from 0 through and including A are marked affected by the normalized record.
  • Microchip SW300052: versions from 0 through and including 2.6 are marked affected by the normalized record.
  • Microchip's advisory describes affected versions as all versions for its affected product set and also names Microchip Library of Applications Crypto and MCC Data Encryption Routines. Those additional products are not present in the normalized affected-products list, so they are not represented here with separate structured ranges.
  • No specific fixed release is identified. Because the normalized record and the advisory describe scope differently, the status of other branches or products outside the ranges above remains unconfirmed.

Technical details

The flaw is in cryptographic implementations that do not provide physical side-channel resistance. Microchip states that the lack of side-channel resistance can allow extraction of keys and data, including keys stored in device memory. The established attack condition is physical access to the system together with the ability to perform side-channel attacks; no network input or user-supplied payload is identified. The record characterizes the attack as high complexity, requiring no privileges and no user interaction. The product pages associate AN1044 with TDES and AES implementations for PIC24 and dsPIC devices, AN953 with encryption routines for PIC18 devices, and SW300052 with the corresponding libraries and additional encryption implementations. The advisory does not identify the specific vulnerable routine, leakage source, measurement method, or extraction procedure, so those implementation details remain unknown.

Exploitability

  • Reachability: The attack requires physical access to the system or device.
  • Preconditions: An attacker must perform side-channel measurements or analysis; the supplied assessment characterizes this condition as high complexity.
  • Authentication and interaction: No privileges and no user interaction are required according to the supplied assessment.
  • Known status: The record does not provide a known-exploited, public-exploit, or ransomware-campaign status. The absence of those statuses is not evidence that exploitation does not exist.

Technical impact

The primary technical outcome is loss of confidentiality through side-channel extraction of keys and data from the cryptographic implementations. Microchip specifically states that keys stored in device memory may be obtained when an attacker has physical access. The supplied assessment indicates confidentiality impact to the vulnerable component and possible confidentiality impact to a subsequent system; the actual scope depends on how the keys are used in deployment. No integrity or availability impact is identified in the supplied assessment. Exposed keys could undermine data protection or require organizational changes to keys and security architecture, but no specific breach is confirmed.

Business impact

  • Extraction of a symmetric or private key can expose protected data and weaken the trust model of devices or services that depend on the key.
  • If a key is reused across devices, communication channels, or subsequent systems, disclosure could have a broader impact; that consequence is possible and deployment-dependent, not a confirmed breach scenario.
  • Operational consequences may include replacing keys, reprovisioning devices, or changing the cryptographic architecture when side-channel resistance is required.
  • The advisory does not identify a specific deployment, victim, or data incident.

Remediation

  1. When symmetric or private keys are used in a system or component that is not physically secured, and loss of the keys would have greater impact than loss of the system or component, use a solution that implements physical and side-channel attack countermeasures, as Microchip recommends.
  2. Do not treat a routine upgrade within the same product family as a confirmed fix. The available evidence identifies no fixed release, and Microchip states that no mitigation is provided because side-channel prevention is outside the intended use of the products.
  3. Reassess key handling, key storage, and physical-security requirements for each deployment before continuing to use the affected implementations.
  4. The normalized record marks patch availability as true, but the supplied solution and Microchip advisory provide no specific patch or fixed release. Confirm product-specific remediation with the vendor if required, and track updates that clarify the affected products or branches.

Detection

  1. Inventory firmware, source code, and build artifacts to identify direct or indirect use of Microchip AN1044, AN953, or SW300052.
  2. Record the deployed release and compare it with the affected boundaries in the affected summary.
  3. Determine whether symmetric keys or private keys are used with these implementations, especially where keys may be stored in device memory.
  4. Review the physical security of each device and determine whether an unauthorized person could access, disassemble, or measure it.
  5. No specific IOC, log event, or telemetry is identified by the advisory. Routine monitoring is only a precaution, and the absence of suspicious logs does not establish that a system is safe.
Sources (8)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.