dbcve.org
CWE-331Weakness · CWE-331

CVE-2026-4930

HIGH · 7.1 CVSS v4.0 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SYMCRYPTO is the SiXG301's host side hardware engine accessed by PSA crypto library that accelerates symmetric cryptographic operations (AES encryption/decryption and hashing). DPA Countermeasures on SYMCRYPTO can be weakened (reduced entropy) by forcing certain seed values if an attacker gains code execution capability on the impacted device. * Therefore, the keys loaded on SYMCRYPTO may be more vulnerable to extraction through DPA attacks than intended

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The SYMCRYPTO hardware engine (SiXG301) used for AES encryption/decryption and hashing has DPA (Differential Power Analysis) countermeasures that can be weakened by forcing specific seed values, reducing entropy. An attacker with code execution capability on the device can exploit this to make cryptographic keys more vulnerable to DPA-based extraction attacks.

MitigationDeploy vendor firmware/patch for SiXG301 to restore full DPA countermeasure entropy. If no patch available, consider isolating affected crypto operations or implementing software-based DPA mitigations as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:P/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SYMCRYPTO SiXG301 hardware engine presence
    Examine system hardware documentation, device inventory, or use commands to query the crypto processor (e.g., lspci, vendor-specific diagnostic tools, or check boot logs for SiXG301 initialization messages)
    Affected if The system contains or utilizes the SiXG301 SYMCRYPTO hardware crypto engine
  2. Confirm AES or hashing operations use the hardware engine
    Review application or system configuration to determine whether cryptographic operations (AES encryption/decryption or hashing functions) are routed through the SiXG301 hardware engine rather than software implementations
    Affected if AES or hashing operations are processed by the SiXG301 hardware engine
  3. Check SiXG301 firmware version
    Query the firmware version of the SiXG301 chip using vendor-provided tools, diagnostic interfaces, or examine relevant system registers/memory where version information is exposed
    Affected if The firmware version is older than the patched version that restores full DPA countermeasure entropy (compare against vendor release notes for CVE-2026-4930)
  4. Verify seed value configuration for DPA countermeasures
    Examine the configuration or memory settings related to DPA countermeasure initialization to determine if external or predictable seed values can influence the entropy source
    Affected if DPA countermeasure seed values are externally controllable, user-configurable, or derived from low-entropy sources

The environment is affected if it uses the SiXG301 SYMCRYPTO hardware engine for AES or hashing with a firmware version lacking the CVE-2026-4930 fix and with DPA countermeasure entropy that can be reduced through seed value manipulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy vendor firmware/patch for SiXG301 to restore full DPA countermeasure entropy. If no patch available, consider isolating affected crypto operations or implementing software-based DPA mitigations as a temporary workaround.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data