CVE-2026-14162
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 · uneditedHospital Queuing Management developed by Advantech has a Sensitive Data Exposure vulnerability, allowing unauthenticated remote attackers to access a specific URL to obtain API documentation.
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 Hospital Queuing Management system by Advantech exposes API documentation through a specific URL without requiring authentication, allowing unauthenticated remote attackers to obtain sensitive technical information about the system's APIs.
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.
-
Check if API documentation endpoints are publicly accessibleAttempt to access common API documentation paths such as /api/docs, /swagger, /swagger-ui, /api-docs, /v1/api-docs, or /documentation on the Hospital Queuing Management system from an unauthenticated network location (or using curl/浏览器 without providing credentials)Affected if API documentation pages load and display API endpoint details without requiring login or authentication credentials
-
Verify authentication requirement on documentation URLsUse a tool like curl to send HTTP GET requests to suspected API doc endpoints (e.g., curl -I http://target/api-docs) and examine the HTTP response status and headers - check if a login page or 401/403 is returned versus actual documentation contentAffected if HTTP response returns 200 OK with API documentation content instead of redirecting to a login page or returning an authentication error
-
Inspect network exposure of documentation endpointsReview firewall rules, reverse proxy configuration, or web server access controls to determine if API documentation paths are exposed to unauthenticated or public network access rather than restricted to internal/admin networksAffected if Documentation endpoints are reachable from unauthenticated/public network segments without IP restrictions or authentication barriers
-
Check for exposed technical information in API docsIf documentation is accessible, examine the content for sensitive details such as internal API endpoints, parameter structures, authentication requirements, or backend service information that should not be publicly disclosedAffected if API documentation reveals technical details about the system's APIs, data structures, or internal functionality to unauthenticated users
The environment is affected if API documentation endpoints for the Advantech Hospital Queuing Management system are accessible without authentication, allowing attackers to gather sensitive technical information about the system's APIs.
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 dataRestrict access to API documentation endpoints by implementing authentication requirements, or remove/disable exposed API documentation from production deployments if not needed.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14162 — 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-14162 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