dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-9085

HIGH · 8.8 CVSS v3.1 Published 2026-07-05
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
Incorrect Permission Assignment for Critical Resource, Improper Access Control vulnerability in TUBITAK BILGEM Software Technologies Research Institute Pardus-Parental-Control allows DNS Spoofing. This issue affects Pardus-Parental-Control: from <=0.5.1 before 0.7.0.

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 Pardus-Parental-Control application versions 0.5.1 and earlier contain incorrect permission assignment and improper access control vulnerabilities that allow unauthorized modification of DNS settings, enabling DNS spoofing attacks.

MitigationUpgrade to version 0.7.0 or later. Until then, restrict access to the parental control application and monitor for unauthorized DNS configuration changes.

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. Identify installed version of Pardus-Parental-Control
    Run 'dpkg -l | grep parental-control' or check the application version through the package manager (apt list --installed 2>/dev/null | grep -i parental) or look in /usr/share/applications for the .desktop file and inspect its version metadata
    Affected if The installed version is 0.5.1 or earlier (versions prior to 0.7.0 are vulnerable)
  2. Verify file permissions on DNS configuration files
    Check the permissions on DNS configuration files typically found in /etc/resolv.conf, /etc/dhcp/dhclient.conf, or network manager config files used by the parental control application using 'ls -la <config-file>'
    Affected if Files are writable by users other than root or the application owner (permissions weaker than 644 for config files)
  3. Inspect application access control settings
    Examine the parental control application's configuration directory (commonly /etc/pardus-parental-control/ or similar) for any ACL, permission, or access control configuration files and verify which system users have write access
    Affected if Non-privileged users or users outside an intended admin group have write access to DNS or network configuration settings
  4. Test for improper DNS setting modification
    As a non-root, non-admin user, attempt to modify DNS settings through the parental control application's interface or config files to see if modification is allowed without authentication
    Affected if Non-admin users can modify DNS settings without proper authorization

A user is affected if Pardus-Parental-Control version 0.5.1 or earlier is installed AND DNS configuration files or the application permit unauthorized modification by non-privileged users.

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 to version 0.7.0 or later. Until then, restrict access to the parental control application and monitor for unauthorized DNS configuration changes.

Recommended fix High confidence

0.7.0

  1. Back up the current Pardus-Parental-Control configuration and any custom settings
  2. Obtain the fixed version 0.7.0 from the official TUBITAK BILGEM Pardus repository or official distribution channels
  3. Upgrade the Pardus-Parental-Control package using the system package manager (e.g., apt-get update && apt-get install pardus-parental-control or equivalent Pardus package management command)
  4. After upgrading, verify that the installed version is 0.7.0 using the package manager or application version check
  5. Restart any related services if required by the upgrade process
  6. Test that parental control functionality operates correctly after the upgrade

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-9085 — 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-9085 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