CVE-2026-32960
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 · uneditedSD-330AC and AMC Manager provided by silex technology, Inc. contain an issue with a sensitive information in resource not removed before reuse. An attacker may login to the device without knowing the password by sending a crafted packet.
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 · high confidenceThe SD-330AC device and AMC Manager software fail to properly remove sensitive authentication information from memory or resources before reuse. An attacker can bypass the login mechanism by sending a crafted packet, exploiting this improper handling of credentials or session data that persists inappropriately.
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< 1.50< 5.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SD-330AC device is in useLocate the Silextechnology SD-330AC device on your network or physically inspect hardware labels and management interfacesAffected if The device is a Silextechnology SD-330AC unit
-
Check SD-330AC firmware versionAccess the device web interface or CLI and locate the firmware version information, typically found in System Info or About pagesAffected if Firmware version is below 1.50 (e.g., 1.49, 1.40, etc.)
-
Identify if AMC Manager software is deployedCheck installed applications on servers or workstations for Silextechnology AMC ManagerAffected if AMC Manager software is installed on any system
-
Check AMC Manager versionOpen AMC Manager and navigate to Help > About, or check the installed program's version propertyAffected if AMC Manager version is below 5.1.0 (e.g., 5.0.x, 4.x, etc.)
-
Verify if remote management or network authentication is enabledCheck device and AMC Manager settings for remote access, network authentication, or login features that could accept crafted packetsAffected if Remote management or network authentication interfaces are exposed and enabled
You are affected if you run SD-330AC firmware below 1.50 or AMC Manager below 5.1.0 and have remote/network authentication features enabled that could accept external authentication requests.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.505.1.0
Implement proper clearing of sensitive authentication data from memory after each use, ensure credentials/tokens are not stored in reusable memory locations, and validate all authentication requests properly.
SD-330AC Firmware 1.50 and AMC Manager 5.1.0
- Upgrade SD-330AC firmware to version 1.50 or later
- Upgrade AMC Manager to version 5.1.0 or later
- After upgrade, verify the device is accessible and functioning normally
- Confirm the sensitive information issue is resolved by testing login functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32960 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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