CVE-2026-1344
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 · uneditedTanium addressed an insecure file permissions vulnerability in Enforce Recovery Key Portal.
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 confidenceInsecure file permissions vulnerability in Tanium Enforce Recovery Key Portal allows local attackers to access sensitive files due to overly permissive file system settings. The vulnerability enables reading or modification of files that should be restricted, potentially exposing recovery keys or configuration data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, < 1.62.5CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Tanium Enforce Recovery Key Portal versionCheck the product version through the Tanium console or by querying the installed package using system package management tools (e.g., rpm, dpkg, or the Tanium client command line interface if available)Affected if The installed version is 1.0.0 or higher but lower than 1.62.5
-
Locate the Tanium Enforce installation directoryFind the installation path for Tanium Enforce Recovery Key Portal - common locations include /opt/tanium, /usr/local/tanium, or the directory specified during installation. Use 'find' or 'locate' commands to search for 'enforce' or 'recovery' directories if the installation path is unknownAffected if The installation directory exists and contains the Enforce Recovery Key Portal components
-
Examine file permissions on sensitive directoriesUse 'ls -la' or 'getfacl' commands to list permissions on directories that store recovery keys, configuration files, or sensitive data within the Tanium Enforce installation path. Focus on directories labeled as 'keys', 'recovery', 'config', or similarAffected if Directories containing sensitive data show permissions such as 755, 777, or allow access to users outside the intended owner or group (e.g., world-readable or group-readable for sensitive files)
-
Inspect individual file permissions for sensitive filesCheck permissions on files that may contain recovery keys, passwords, or configuration data using 'ls -la' on specific file types (e.g., .key, .pem, .conf, .xml, .json files in the installation directoryAffected if Sensitive files have permissions such as 644, 655, 755, or higher (less restrictive than 600), allowing unauthorized users to read or modify them
-
Verify ownership of sensitive filesUse 'ls -la' to check the owner and group of sensitive directories and files within the Tanium Enforce installation. Confirm they are owned by the appropriate service account or administrator, not by root or a shared account if multiple services run under different usersAffected if Sensitive files are owned by overly permissive accounts or have group ownership that grants access to unauthorized users
A system is affected if Tanium Enforce Recovery Key Portal version is 1.0.0 or higher but lower than 1.62.5 AND sensitive files or directories within the installation have overly permissive permissions (e.g., world-readable, group-readable, or set to 644/755 or higher instead of 600) that could allow local unauthorized access to recovery keys or configuration data.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.62.5
Apply the vendor patch or update provided by Tanium for the Enforce Recovery Key Portal to remediate the insecure file permissions. Verify that file permissions on sensitive directories and files are set to restrictive levels (e.g., 600 or more restrictive for sensitive files, appropriate ownership).
1.62.5
- Identify the current version of Enforce Recovery Key Portal installed in your environment
- Consult Tanium documentation (security.tanium.com) or contact Tanium support for the official upgrade procedure
- Plan and execute the upgrade to version 1.62.5 or later
- Verify the upgrade was successful by confirming the new version number
- Confirm the insecure file permissions vulnerability is addressed in the upgraded version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1344 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1344 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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