dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-8377

HIGH · 8.2 CVSS v3.1 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 7 weeks old

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
Missing Authorization vulnerability in Armiya Information Technologies Ltd. Co. Access Control System (GKS) allows Collect Data from Common Resource Locations. This issue affects Access Control System (GKS): before Version 2.

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

Missing authorization vulnerability in Armiya Access Control System (GKS) allows unauthorized data collection from common resource locations. The system fails to properly enforce access controls on certain endpoints or storage locations, enabling attackers to retrieve sensitive data without proper authentication or authorization checks.

MitigationImplement proper authorization checks on all data access points and resources. Update to Version 2 or later which contains the fix. Conduct access control audit to ensure all endpoints require valid authentication.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 installed Armiya version
    Locate the version information for your Armiya Access Control System (GKS) installation through the admin interface, system info page, or version file
    Affected if The installed version is Version 1 or earlier (versions prior to the fix)
  2. Test unauthenticated endpoint access
    Attempt to access common resource endpoints or API paths used by the system without providing valid authentication credentials
    Affected if Endpoints return sensitive data or allow data retrieval without any authentication token or session
  3. Verify storage location access controls
    Check whether data storage locations or directories used by the system enforce proper authorization - attempt access without credentials
    Affected if Storage locations are accessible without authentication or authorization verification
  4. Review access control configuration
    Examine the system's access control settings, permissions configuration, or authorization rules for data access points
    Affected if Authorization checks are missing, disabled, or improperly configured for certain data access paths
  5. Confirm endpoint authentication requirement
    Test known endpoints or resource locations referenced by the system to determine if they require valid authentication
    Affected if Endpoints or resources can be reached and return data without requiring any authentication

Your environment is affected if you are running Armiya Access Control System (GKS) Version 1 or earlier, or if data endpoints and storage locations are accessible without proper authentication.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all data access points and resources. Update to Version 2 or later which contains the fix. Conduct access control audit to ensure all endpoints require valid authentication.

Recommended fix Moderate confidence

Version 2

  1. 1. Identify the current version of Armiya Access Control System (GKS) installed in your environment
  2. 2. Obtain Version 2 or later of the Access Control System (GKS) from Armiya Information Technologies Ltd. Co.
  3. 3. Backup all existing configuration data and system state before upgrading
  4. 4. Install Version 2 of the Access Control System (GKS) following vendor-provided installation procedures
  5. 5. Restore or reconfigure system settings as needed after installation
  6. 6. Verify that the upgrade was successful by checking the system version
  7. 7. Test that the authorization controls are properly enforced - specifically verify that unauthenticated or unauthorized users can no longer collect data from common resource locations
  8. 8. Monitor system logs for any authorization-related errors or anomalies
Caveat No explicit breaking changes documented; upgrade is recommended to address the missing authorization vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-8377 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