BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-22701High confidence

filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock

tox-dev · filelock

Official source article: GitHub GHSA-QMGC-5H2G-MVRW ↗. Check the applicable product and release in the original source.

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 137 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 12 Jan 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs tox-dev filelock and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 137 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepython-filelockAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython-filelockVendor fix publishedDebian records a fixed source-package version for this release.3.9.0-1+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython-filelockVendor fix publishedDebian records a fixed source-package version for this release.3.20.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython-filelockVendor fix publishedDebian records a fixed source-package version for this release.3.20.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appspython-filelockVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.13.1-1ubuntu0.1~esm1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIfilelockECOSYSTEM: introduced 0; fixed 3.20.33.20.3OSV record ↗aggregator derived · 10 Sep 2026
pipfilelock< 3.20.33.20.3GitHub advisory ↗upstream repository advisory · 13 Jan 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-22701 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityfilelock: filelock Time-of-Check-Time-of-Use (TOCTOU) in SoftFileLock
136 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • rhmtc/openshift-migration-hook-runner-rhel8 as a component of Migration Toolkit for Containers
  • openshift-lightspeed-tech-preview/lightspeed-rag-tool-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-ocp-rag-rhel9 as a component of OpenShift Lightspeed
  • openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed
  • openshift-service-mesh/grafana-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-cni-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-must-gather-rhel9 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-operator-bundle as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/istio-rhel8-operator as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/pilot-rhel8 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/proxyv2-rhel9 as a component of OpenShift Service Mesh 2
  • openshift-service-mesh/ratelimit-rhel8 as a component of OpenShift Service Mesh 2
Summary
A Time-of-Check-Time-of-Use (TOCTOU) flaw has been discovered in the pypi filelock package. The TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-1870

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 137 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

What

filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Link Resolution Before File Access ('Link Following') → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following'). The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-59
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260114Security Bulletin 14 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 14 Jan 2026, published on 14 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-16439 Référence CVE CVE-2026-16440 https://www.cve.org/CVERecord?id=CVE-2026-16440 Référence CVE CVE-2026-16441 https://www.cve.org/CVERecord?id=CVE-2026-16441 Référence CVE CVE-2026-16728 https://www.cve.org/CVERecord?id=CVE-2026-16728 Référence CVE CVE-2026-16729 https://www.cve.org/CVERecord?id=CVE-2026-16729 Référence CVE CVE-2026-18149 https://www.cve.org/CVERecord?id=CVE-2026-18149 Référence CVE CVE-2026-18446 https://www.cve.org/CVERecord?id=CVE-2026-18446 Référence CVE CVE-2026-18540 https://www.cve.org/CVERecord?id=CVE-2026-18540 Référence CVE CVE-2026-19534 https://www.cve.org/CVERecord?id=CVE-2026-19534 Référence CVE CVE-2026-22701 https://www.cve.org/CVERecord?id=CVE-2026-22701 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-25793 https://www.cve.org/CVERecord?id=CVE-2026-25793 Référence CVE CVE-2026-33891 https://www.cve.org/CVERecord?id=CVE-2026-33891 Référence CVE CVE-2026-33894 https://www.cve.org/CVERecord?id=CVE-2026-33894 Référence CVE CVE-2026-33895 https://www.cve.org/CVERecord?id=CVE-2026-33895 Référence CVE CVE-2026-33896 https://www.cve.org/CVERecord?id=CVE-2026-33896 Référence CVE CVE-2026-34043 https://www.cve.org/CVERecord?id=CVE-2026-34043 Référence CVE CVE-2026-3449 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0736Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-20252 Référence CVE CVE-2026-20253 https://www.cve.org/CVERecord?id=CVE-2026-20253 Référence CVE CVE-2026-20254 https://www.cve.org/CVERecord?id=CVE-2026-20254 Référence CVE CVE-2026-20255 https://www.cve.org/CVERecord?id=CVE-2026-20255 Référence CVE CVE-2026-20256 https://www.cve.org/CVERecord?id=CVE-2026-20256 Référence CVE CVE-2026-20257 https://www.cve.org/CVERecord?id=CVE-2026-20257 Référence CVE CVE-2026-20258 https://www.cve.org/CVERecord?id=CVE-2026-20258 Référence CVE CVE-2026-20259 https://www.cve.org/CVERecord?id=CVE-2026-20259 Référence CVE CVE-2026-20260 https://www.cve.org/CVERecord?id=CVE-2026-20260 Référence CVE CVE-2026-22701 https://www.cve.org/CVERecord?id=CVE-2026-22701 Référence CVE CVE-2026-23490 https://www.cve.org/CVERecord?id=CVE-2026-23490 Référence CVE CVE-2026-24049 https://www.cve.org/CVERecord?id=CVE-2026-24049 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-25679 https://www.cve.org/CVERecord?id=CVE-2026-25679 Référence CVE CVE-2026-27142 https://www.cve.org/CVERecord?id=CVE-2026-27142 Référence CVE CVE-2026-27448 https://www.cve.org/CVERecord?id=CVE-2026-27448 Référence CVE CVE-2026-27459 https://www.cve.org/CVERecord?id=CVE-2026-27459 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-21998 Référence CVE CVE-2026-22001 https://www.cve.org/CVERecord?id=CVE-2026-22001 Référence CVE CVE-2026-22002 https://www.cve.org/CVERecord?id=CVE-2026-22002 Référence CVE CVE-2026-22004 https://www.cve.org/CVERecord?id=CVE-2026-22004 Référence CVE CVE-2026-22005 https://www.cve.org/CVERecord?id=CVE-2026-22005 Référence CVE CVE-2026-22009 https://www.cve.org/CVERecord?id=CVE-2026-22009 Référence CVE CVE-2026-22015 https://www.cve.org/CVERecord?id=CVE-2026-22015 Référence CVE CVE-2026-22017 https://www.cve.org/CVERecord?id=CVE-2026-22017 Référence CVE CVE-2026-22022 https://www.cve.org/CVERecord?id=CVE-2026-22022 Référence CVE CVE-2026-22701 https://www.cve.org/CVERecord?id=CVE-2026-22701 Référence CVE CVE-2026-22731 https://www.cve.org/CVERecord?id=CVE-2026-22731 Référence CVE CVE-2026-22732 https://www.cve.org/CVERecord?id=CVE-2026-22732 Référence CVE CVE-2026-22733 https://www.cve.org/CVERecord?id=CVE-2026-22733 Référence CVE CVE-2026-22735 https://www.cve.org/CVERecord?id=CVE-2026-22735 Référence CVE CVE-2026-22737 https://www.cve.org/CVERecord?id=CVE-2026-22737 Référence CVE CVE-2026-22815 https://www.cve.org/CVERecord?id=CVE-2026-22815 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-2332 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0315Multiples vulnérabilités dans les produits VMware

VERecord?id=CVE-2026-2003 Référence CVE CVE-2026-2004 https://www.cve.org/CVERecord?id=CVE-2026-2004 Référence CVE CVE-2026-2005 https://www.cve.org/CVERecord?id=CVE-2026-2005 Référence CVE CVE-2026-2006 https://www.cve.org/CVERecord?id=CVE-2026-2006 Référence CVE CVE-2026-21637 https://www.cve.org/CVERecord?id=CVE-2026-21637 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-22701 https://www.cve.org/CVERecord?id=CVE-2026-22701 Référence CVE CVE-2026-22702 https://www.cve.org/CVERecord?id=CVE-2026-22702 Référence CVE CVE-2026-22703 https://www.cve.org/CVERecord?id=CVE-2026-22703 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-23831 https://www.cve.org/CVERecord?id=CVE-2026-23831 Référence CVE CVE-2026-24117 https://www.cve.org/CVERecord?id=CVE-2026-24117 Référence CVE CVE-2026-24137 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0224Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2026-1615 Référence CVE CVE-2026-21860 https://www.cve.org/CVERecord?id=CVE-2026-21860 Référence CVE CVE-2026-21925 https://www.cve.org/CVERecord?id=CVE-2026-21925 Référence CVE CVE-2026-21932 https://www.cve.org/CVERecord?id=CVE-2026-21932 Référence CVE CVE-2026-21933 https://www.cve.org/CVERecord?id=CVE-2026-21933 Référence CVE CVE-2026-21945 https://www.cve.org/CVERecord?id=CVE-2026-21945 Référence CVE CVE-2026-22610 https://www.cve.org/CVERecord?id=CVE-2026-22610 Référence CVE CVE-2026-22690 https://www.cve.org/CVERecord?id=CVE-2026-22690 Référence CVE CVE-2026-22691 https://www.cve.org/CVERecord?id=CVE-2026-22691 Référence CVE CVE-2026-22701 https://www.cve.org/CVERecord?id=CVE-2026-22701 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Gestion détaillée du document le 27 février 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-006446tox-devのfilelockにおける複数の脆弱性

filelockはPythonのプラットフォームに依存しないファイルロックです。バージョン3.20.3以前には、filelockパッケージのSoftFileLock実装にTOCTOU競合状態の脆弱性が存在していました。ローカルファイルシステムへのアクセス権があり、シンボリックリンクの作成権限を持つ攻撃者は、権限検証とファイル作成の間の競合状態を悪用して、ロック操作の失敗または予期しない動作を引き起こす可能性があります。この脆弱性は_acquire()メソッド内のraise_on_not_writable_file()（権限チェック）とos.open()（ファイル作成）の間で発生します。この競合ウィンドウの間に攻撃者はロックファイルパスにシンボリックリンクを作成でき、そのためロックが意図しないターゲットファイルで動作したり、サービス拒否を引き起こしたりします。この問題はバージョン3.20.3で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 10 Jan 2026 · Last source change 12 Jan 2026, 16:45 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-1870
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-1870↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-QMGC-5H2G-MVRW↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-22701 · cve.blacktree.nl