CVE-2026-7852
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 · uneditedUnrestricted upload of file with dangerous type vulnerability in Limatek System Inc. LimRAD NAC allows Remote Code Inclusion. This issue affects LimRAD NAC: before 5.5.7.3.9.
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 confidenceThe LimRAD NAC product contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types. Since the uploaded files can be executed server-side, this leads to Remote Code Execution (RCE). The vulnerability exists in versions prior to 5.5.7.3.9.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the installed LimRAD NAC versionLocate the version information for LimRAD NAC (typically in the admin interface, about page, or system information panel). This may be accessible via the web UI, a configuration file, or a command-line tool provided by the product.Affected if The installed version is lower than 5.5.7.3.9 (for example, 5.5.7.3.8, 5.5.6.x, or earlier). Compare your version string against this threshold.
-
Locate the file upload functionalityIdentify whether the LimRAD NAC product exposes a file upload feature. This may be in the admin interface, a guest registration portal, a device onboarding page, or an API endpoint. Look for forms or APIs that accept file submissions.Affected if The file upload functionality is present and accessible to unauthenticated users or low-privilege accounts.
-
Determine the upload directory configurationExamine the configuration of the directory where uploaded files are stored. Check if the web server (for example, Apache, Nginx, or IIS) is configured to allow script execution (PHP, JSP, ASP, CGI, etc.) within that directory.Affected if Script execution is enabled in the upload directory (for example, AddType or ExecCGI directives are active, or the directory lacks restrictions preventing execution of uploaded files).
-
Check for file type validation controlsInspect the upload mechanism to see if there is any server-side file type validation. Look for allowlists of permitted extensions, MIME type checks, or magic byte verification in the application configuration or source code.Affected if No server-side file type validation exists, or the validation can be bypassed (for example, only client-side checks are present, or dangerous extensions like .php, .jsp, .asp are not explicitly blocked).
A user is affected if their LimRAD NAC version is below 5.5.7.3.9 AND the file upload feature is accessible to attackers with little or no authentication.
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 · scopedUpgrade to LimRAD NAC version 5.5.7.3.9 or later. If immediate patching is not feasible, implement file type validation (allowlist approach), disable script execution in upload directories, and restrict upload functionality to authenticated, authorized users.
5.5.7.3.9 or later
- Identify all deployments of Limatek System Inc. LimRAD NAC in the environment
- Check current version of LimRAD NAC installations
- For versions before 5.5.7.3.9, obtain the updated version from the vendor (5.5.7.3.9 or later)
- Schedule maintenance window following change management procedures
- Backup current configuration and any custom settings
- Apply upgrade to version 5.5.7.3.9 or later following vendor documentation
- Verify the upgrade was successful and system is operational
- Confirm vulnerability is remediated by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2026-7852 — 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-7852 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