dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2026-23648

HIGH · 7.8 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Glory RBG-100 recycler systems using the ISPK-08 software component contain multiple system binaries with overly permissive file permissions. Several binaries executed by the root user are writable and executable by unprivileged local users. An attacker with local access can replace or modify these binaries to execute arbitrary commands with root privileges, enabling local privilege escalation.

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 · high confidence

The Glory RBG-100 recycler systems running ISPK-08 software contain multiple system binaries with overly permissive file permissions. Unprivileged local users can write to and execute binaries that run with root privileges, enabling them to inject malicious code and achieve local privilege escalation.

MitigationRestrict write permissions on system binaries to root-only, ensuring unprivileged users cannot modify executables. Verify all binaries in privileged paths have appropriate ownership and permission settings.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify system product and software version
    Check if the system is a Glory RBG-100 recycler running ISPK-08 software. Run 'uname -a' or check /etc/os-release if available, and look for ISPK-08 in system information or firmware version files.
    Affected if The system is a Glory RBG-100 running ISPK-08 software.
  2. Locate system binary directories
    Identify paths containing system executables: /sbin, /usr/sbin, /bin, /usr/bin, /usr/local/bin, and any vendor-specific binary paths such as /opt/glory/bin or /app/bin if they exist.
    Affected if The system uses standard or vendor-specific binary directories that may contain privileged executables.
  3. Check binary file permissions for world-writable files
    Run 'find /sbin /usr/sbin /bin /usr/bin -type f -perm -002 2>/dev/null' to locate all world-writable executables, or use 'ls -la <binary_path>' on specific binaries to inspect permission bits.
    Affected if Any system binary in privileged paths is world-writable (permission includes 'o+w').
  4. Check binary file permissions for group-writable files
    Run 'find /sbin /usr/sbin /bin /usr/bin -type f -perm -020 2>/dev/null' to locate all group-writable executables, or check ownership and group permissions on binaries in key directories.
    Affected if Any system binary in privileged paths is group-writable (permission includes 'g+w').
  5. Identify SUID/SGID binaries with permissive permissions
    Run 'find /sbin /usr/sbin /bin /usr/bin -type f \( -perm -4000 -o -perm -2000 \) -perm -002 2>/dev/null' to find SUID/SGID executables that are also writable by non-owners.
    Affected if A binary runs with root privileges (SUID/SGID) and is writable by non-root users.
  6. Verify binary ownership
    Use 'ls -la' on key system binaries to check if they are owned by root. Then compare with write permissions for other users using 'stat <binary_path>' or 'getfacl <binary_path>' if available.
    Affected if Critical system binaries are owned by root but allow write access from unprivileged users.

A system is affected if it is a Glory RBG-100 running ISPK-08 software AND contains any system binaries in privileged paths that are writable by non-root users, especially SUID/SGID binaries.

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

Restrict write permissions on system binaries to root-only, ensuring unprivileged users cannot modify executables. Verify all binaries in privileged paths have appropriate ownership and permission settings.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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