Sd 330ac FirmwareOperating system · Silextechnology

CVE-2026-32958

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-20
Fix available
A fix is available. Upgrade to 1.50 / 5.1.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
SD-330AC and AMC Manager provided by silex technology, Inc. use a hard-coded cryptographic key. An administrative user may be directed to apply a fake firmware update.

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 SD-330AC device and AMC Manager software from silex technology contain a hard-coded cryptographic key used in their firmware update verification mechanism. An attacker who social-engineers an administrative user into applying a malicious firmware update can bypass cryptographic validation due to this static key, allowing execution of unauthorized firmware.

MitigationContact silex technology for patched firmware that removes hardcoded keys; verify all firmware updates originate from official vendor sources before installation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sd 330ac FirmwareOperating system
Affected:< 1.50
Amc ManagerApplication
Affected:< 5.1.0

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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. Check SD-330AC device firmware version
    Access the device web interface or administrative console and locate the firmware version information, typically found under System, Status, or Firmware Update sections
    Affected if Firmware version is displayed as less than 1.50
  2. Check AMC Manager software version
    Open AMC Manager and navigate to Help > About, or check the installed program's version property in the Windows Programs and Features list
    Affected if AMC Manager version is less than 5.1.0
  3. Determine if firmware update feature is accessible
    Check if the device administrative interface includes a firmware update or firmware upgrade option, and verify whether the update mechanism uses cryptographic verification
    Affected if Firmware update feature exists and uses a static verification key rather than per-device or dynamically generated keys

You are affected if the SD-330AC firmware is below version 1.50 or AMC Manager is below version 5.1.0, and the firmware update mechanism relying on the hardcoded key is enabled on your device.

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.

dbcve · scoped
Upgrade available Upgrade to 1.50 / 5.1.0 or later
Fixed in 1.505.1.0
Interim mitigation

Contact silex technology for patched firmware that removes hardcoded keys; verify all firmware updates originate from official vendor sources before installation.

Recommended fix High confidence

SD-330AC Firmware 1.50; AMC Manager 5.1.0

  1. Obtain the SD-330AC firmware version 1.50 or later from the official silex technology support website
  2. Obtain AMC Manager version 5.1.0 or later from the official silex technology support website
  3. Follow the official silex technology firmware update procedure to upgrade the SD-330AC device to firmware version 1.50 or later
  4. Follow the official silex technology software update procedure to upgrade AMC Manager to version 5.1.0 or later
  5. Verify that the upgraded versions are correctly installed by checking the firmware version on the SD-330AC and the software version of AMC Manager

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd 330ac Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-32958 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