dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-14460

HIGH · 8.8 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 TUBITAK BILGEM Software Technologies Research Institute pardus-software allows Argument Injection. This issue affects pardus-software: from <= 1.0.4 before 1.0.5.

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 in pardus-software <= 1.0.4 allows unauthenticated attackers to inject arbitrary arguments into system commands. This authorization bypass combined with argument injection could enable command execution with the privileges of the affected application.

MitigationUpgrade pardus-software to version 1.0.5 or later. If upgrade is not immediately possible, restrict network access to the affected component and audit all input handling for proper authorization checks.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Verify pardus-software is installed
    Query the system package manager for pardus-software (e.g., rpm -qa | grep pardus, dpkg -l | grep pardus, or listing installed packages). If not a package, search for pardus-software binary or service processes running on the system.
    Affected if pardus-software is found installed or running on the system
  2. Determine installed version
    Use the package manager query to retrieve the exact version number (e.g., rpm -q pardus-software --queryformat '%{VERSION}', dpkg -s pardus-software). If no package, check any --version or -v flag the binary may support.
    Affected if Installed version is 1.0.4 or lower (any version up to and including 1.0.4)
  3. Check network exposure
    Identify if pardus-software exposes any network service, API endpoint, or web interface. Review any configuration files for listen addresses, port settings, or enabled server modules. Check listening network ports (netstat, ss) for pardus-software related processes.
    Affected if The software listens on network-accessible interfaces (0.0.0.0 or any non-loopback address) and accepts unauthenticated requests
  4. Identify execution privileges
    Check under what user/context pardus-software runs (ps aux, service configuration, systemd unit files). Look for elevated privileges or access to sensitive system resources.
    Affected if Software runs with root privileges or has access to sensitive system capabilities that could be leveraged upon successful exploitation

Environment is affected if pardus-software version 1.0.4 or lower is installed and exposes network-accessible interfaces that accept unauthenticated requests, allowing argument injection into system commands.

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

Upgrade pardus-software to version 1.0.5 or later. If upgrade is not immediately possible, restrict network access to the affected component and audit all input handling for proper authorization checks.

Recommended fix High confidence

pardus-software version 1.0.5

  1. 1. Identify all systems running pardus-software version 1.0.4 or earlier
  2. 2. Backup current configuration and data
  3. 3. Obtain pardus-software version 1.0.5 from official TUBITAK BILGEM repositories
  4. 4. Upgrade pardus-software to version 1.0.5
  5. 5. Verify the upgrade was successful by checking the software version
  6. 6. Test that normal functionality works as expected
  7. 7. Confirm the vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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