Improper Access ControlWeakness · CWE-284

CVE-2026-1749

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges 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
There is an Access Control Vulnerability in some HikCentral Professional versions. This could allow an unauthenticated user to obtain the admin permission.

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

This is an access control vulnerability in HikCentral Professional that allows an unauthenticated user to gain administrative privileges. The vulnerability represents a critical privilege escalation flaw where the access control mechanism can be bypassed, permitting unauthorized users to obtain full admin access to the system.

MitigationApply vendor-supplied patches or updates to HikCentral Professional to remediate the access control vulnerability. If patches are unavailable, implement network segmentation and restrict access to the management interface to trusted IP addresses.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

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. Identify HikCentral Professional installation and version
    Locate the HikCentral Professional installation on the system. Check the management interface (System > About) or the installation directory for version information. The version is typically displayed in the system info or help/about section.
    Affected if Version matches unpatched releases and the authentication/authorization module is in use
  2. Determine web service exposure
    Check network configuration to see if HikCentral Professional web portal or API endpoints are accessible from network interfaces. Look for port 443 or 8443 bindings and firewall rules.
    Affected if The HikCentral Professional web interface is exposed to untrusted or public networks without VPN or IP restrictions
  3. Audit administrator accounts
    Review user management in HikCentral Professional (typically under System > User Management or Security > Users) for any admin-level accounts that were not created by legitimate administrators.
    Affected if Unexpected administrator accounts exist or account creation timestamps correlate with potential attack periods
  4. Examine authentication logs for privilege escalation
    Search HikCentral Professional audit and security logs for events indicating privilege level changes, particularly from unauthenticated or standard user context to administrator role.
    Affected if Logs show unauthorized privilege escalation attempts or successful escalations from unauthenticated sessions
  5. Verify authorization configuration
    Check the security/authorization settings in HikCentral Professional to confirm whether role-based access control (RBAC) is properly enforced for all API endpoints and administrative functions.
    Affected if Authorization checks are missing or disabled for critical administrative functions

Environment is affected if HikCentral Professional is running with unpatched versions, has its web interface exposed to untrusted networks, and shows evidence of unauthorized admin account creation or privilege escalation activity in logs or configuration.

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

Apply vendor-supplied patches or updates to HikCentral Professional to remediate the access control vulnerability. If patches are unavailable, implement network segmentation and restrict access to the management interface to trusted IP addresses.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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