CVE-2025-10461
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 · uneditedGlobal file reads caused by improper URL checks in webserver in Softing Industrial Automation GmbH smartLinks on docker (filesystem modules) allows file access. This issue affects smartLink SW-HT: through 1.42 smartLink SW-PN: through 1.03.
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 confidenceThis is a path traversal vulnerability in the webserver component of Softing Industrial Automation GmbH's smartLink SW-HT (through v1.42) and smartLink SW-PN (through v1.03) docker deployments. The webserver fails to properly validate URL inputs, allowing attackers to use directory traversal sequences (e.g., ../../../) to access files outside the intended web root directory. This enables unauthenticated remote attackers to read arbitrary files on the host system.
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
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- Y
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/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:Y/R:A/V:X/RE:L/U:Green
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 deployed smartLink productList running Docker containers and identify if smartLink SW-HT or smartLink SW-PN is running: docker ps -a | grep -i smartlinkAffected if Container named smartLink SW-HT or smartLink SW-PN is present
-
Check smartLink SW-HT versionInspect the docker container image or running container for version information: docker inspect <container_id> | grep -i version or check container labels/tagsAffected if Version is at or below 1.42 for SW-HT
-
Check smartLink SW-PN versionInspect the docker container image or running container for version information: docker inspect <container_id> | grep -i version or check container labels/tagsAffected if Version is at or below 1.03 for SW-PN
-
Verify webserver component is exposedCheck if the webserver port is exposed and accessible externally: docker ps --format '{{.Ports}}' | grep -E '80|443|8080|8443' or inspect container port mappingsAffected if Webserver ports (HTTP/HTTPS) are mapped to host interfaces and reachable from network
Environment is affected if running a docker deployment of smartLink SW-HT v1.42 or earlier, or smartLink SW-PN v1.03 or earlier, with the webserver interface network-accessible.
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.
From vendor dataApply vendor-provided patches when available; until then, restrict network access to the docker webserver interface and implement web application firewall rules to block traversal patterns in URLs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10461 — 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-2025-10461 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