Improper Input ValidationWeakness · CWE-20

CVE-2026-47367

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
A malicious actor with access to the network and low privileges could exploit an Improper Input Validation vulnerability found in UID Enterprise Agent to execute a Command Injection on the host 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 · moderate confidence

Improper input validation in UID Enterprise Agent allows a low-privileged attacker with network access to inject and execute arbitrary commands on the host system. This represents a significant privilege escalation vector from low-privilege access to full command execution.

MitigationImplement strict input validation and sanitization for all user-supplied input in the UID Enterprise Agent, and apply vendor-provided patches immediately upon release.

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
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm UID Enterprise Agent installation
    Search for the UID Enterprise Agent process or service on the host system. Check for running processes named 'uid-agent', 'enterprise-agent', or similar patterns. On Windows, check Services for 'UID Enterprise Agent'. On Linux, use 'ps aux | grep -i uid' or check systemd services.
    Affected if The UID Enterprise Agent software is present and running on the system
  2. Identify installed version
    Locate the agent binary or application directory and query its version. Common methods: 'uid-agent --version', check a VERSION file in the installation directory, or right-click the executable and view Properties > Details. Record the exact version string.
    Affected if The installed version cannot be determined or is older than the vendor-provided patched version
  3. Verify network exposure of the agent
    Check if the UID Enterprise Agent listens on any network ports. Use 'netstat -anp | grep -i uid' or 'ss -tlnp | grep -i uid' on Linux. On Windows, run 'netstat -ano | findstr /i uid' or check listening ports via PowerShell Get-NetTCPConnection.
    Affected if The agent is bound to a network interface and accessible from non-localhost addresses
  4. Assess authentication and input handling
    Examine the agent configuration files for authentication settings and input validation parameters. Check the installation directory for config files (often XML, JSON, or YAML) and look for settings related to input validation, command handling, or API endpoints.
    Affected if The agent allows unauthenticated or weakly authenticated input that could be supplied by low-privilege users
  5. Review access controls
    Determine what user privileges are required to interact with the agent's input interfaces. Check if the agent exposes any API, CLI, or web interface that accepts user-supplied data. Review the documentation or configuration for role-based access control settings.
    Affected if Low-privilege users or unauthenticated actors can submit input to the agent

The environment is affected if UID Enterprise Agent is installed, network-accessible, and accepts input from low-privilege users without proper validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for all user-supplied input in the UID Enterprise Agent, and apply vendor-provided patches immediately upon release.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47367 — 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-47367 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