CVE-2026-32955
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 a stack-based buffer overflow vulnerability in processing the redirect URLs. Arbitrary code may be executed on the device.
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 confidenceSD-330AC and AMC Manager by silex technology contain a stack-based buffer overflow vulnerability in redirect URL processing. The overflow allows attackers to overwrite stack memory and execute arbitrary code on the affected device.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 SD-330AC device on networkScan network for devices responding on HTTP (port 80/443) or telnet (port 23) that identify as Silex SD-330AC. Check DHCP lease tables or network scans for MAC vendor prefix 00:1A:8B (Silex) or device hostname.Affected if SD-330AC device is present on the network with web or telnet access
-
Check SD-330AC firmware versionAccess the device web interface and navigate to Status or System > Firmware version page. Alternatively, use telnet/SSH to connect and run command: 'show version' or 'sysinfo'. The firmware version is displayed as a numeric value (e.g., 1.42).Affected if Firmware version is lower than 1.50 (for example, 1.42, 1.30, etc.)
-
Identify AMC Manager installationOn Windows, open Control Panel > Programs and Features, or use PowerShell: 'Get-WmiObject -Class Win32_Product | Select-Object Name,Version'. Look for 'AMC Manager' or 'Silex AMC Manager' in the installed software list.Affected if AMC Manager software is installed on the system
-
Check AMC Manager versionIn the AMC Manager application, click Help > About. The version number is displayed (for example, 5.0.8). Alternatively, check the installation directory for version info in the executable properties.Affected if AMC Manager version is lower than 5.1.0 (for example, 5.0.8, 4.2.1, etc.)
-
Verify web interface is accessible for redirect processingConfirm the device web management interface is reachable over HTTP/HTTPS. The vulnerability exists in redirect URL processing, which is a web-based function. Check if ports 80 or 443 are open and responding.Affected if Web management interface is exposed and accessible to network users
You are affected if you have a SD-330AC device with firmware below 1.50 or AMC Manager software below version 5.1.0, and the web management interface is accessible on the network.
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
Apply vendor-supplied patches when available. Until then, restrict network access to device management interfaces and implement network segmentation to limit exposure.
SD-330AC Firmware >= 1.50 or AMC Manager >= 5.1.0
- Identify the affected product (SD-330AC firmware or AMC Manager) in your environment
- Navigate to the official silex technology support website (www.silex.jp)
- Locate the download section for SD-330AC or AMC Manager
- Download firmware version 1.50 or higher for SD-330AC, or version 5.1.0 or higher for AMC Manager
- Review the firmware upgrade instructions provided by silex technology
- Apply the firmware update following the vendor's documented procedure
- Verify the version has been successfully updated after applying the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32955 — 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-32955 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