BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-45582High confidence

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process

GNU · Tar

4.1MediumCVSS 3.1
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.49% 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.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs GNU Tar 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: As exposure requiresRemediation target: Within 365 days

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.

Distribution package intelligence

Release-specific package status

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

1 package state
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
Ubuntu 24.04 LTSnoble · standard archivetarVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.35+dfsg-3ubuntu0.2Canonical Ubuntu Security ↗Source updated 5 Oct 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.

2 current
CVE-2025-45582 · CSAF 2.0 · revision 41 · interimSUSE Product Security TeamCVE-2025-45582
90 known affected

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

  • tar as component of SLES-LTSS-TERADATA 15 SP2
  • tar as component of SUSE Linux Enterprise Desktop 15 SP6
  • tar-lang as component of SUSE Linux Enterprise Desktop 15 SP6
  • tar-rmt as component of SUSE Linux Enterprise Desktop 15 SP6
  • tar as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • tar-lang as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • tar-rmt as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • tar as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • tar-lang as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • tar-rmt as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • tar as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • tar-lang as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
Summary
GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-45582 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitytar: Tar path traversal
5 known affected

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

  • tar.src as a component of Red Hat Enterprise Linux 6
  • tar.src as a component of Red Hat Enterprise Linux 7
  • io.syndesis-syndesis-ui as a component of Red Hat Fuse 7
  • openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in GNU Tar. An attacker could exploit this vulnerability by providing two specially crafted TAR archives, if those archives were extracted in the same directory. The first archive contains a symbolic link that points to a critical directory. The second archive, when extracted, uses this symbolic link to overwrite sensitive files on the system, bypassing existing directory traversal protections. This could lead to unauthorized file modification or, in some cases, privilege escalation.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-2025-21178

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 actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

What

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

Why

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize ../ sequences that can resolve to a location that is outside of that directory.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.

Why

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize ../ sequences that can resolve to a location that is outside of that directory.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Path Traversal: '../filedir' → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-24 ↗

CWE-24: Path Traversal: '../filedir'. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize ../ sequences that can resolve to a location that is outside of that directory.

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:N/UI:R/S:C/C:N/I:L/A:L

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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited 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.
UnauthenticatedCWE-24Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1730Xerox FreeFlow Print Server: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0008Red Hat Enterprise Linux: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux bezüglich der Komponenten "tar" und "Scrapy" ausnutzen, um Dateien zu manipulieren, und um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250716Security Bulletin 16 Jul 2025 [922 KB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 16 Jul 2025 [922 KB], published on 16 July 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ord?id=CVE-2025-40356 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4575 https://www.cve.org/CVERecord?id=CVE-2025-4575 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-46727 https://www.cve.org/CVERecord?id=CVE-2025-46727 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-2025-47153 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-20

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

ord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47153 https://www.cve.org/CVERecord?id=CVE-2025-47153 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47908 https://www.cve.org/CVERecord?id=CVE-

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

ERecord?id=CVE-2025-30754 Référence CVE CVE-2025-31651 https://www.cve.org/CVERecord?id=CVE-2025-31651 Référence CVE CVE-2025-32988 https://www.cve.org/CVERecord?id=CVE-2025-32988 Référence CVE CVE-2025-32989 https://www.cve.org/CVERecord?id=CVE-2025-32989 Référence CVE CVE-2025-32990 https://www.cve.org/CVERecord?id=CVE-2025-32990 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3360 Référence CVE CVE-2025-37727 https://www.cve.org/CVERecord?id=CVE-2025-37727 Référence CVE CVE-2025-3887 https://www.cve.org/CVERecord?id=CVE-2025-3887 Référence CVE CVE-2025-4056 https://www.cve.org/CVERecord?id=CVE-2025-4056 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4565 https://www.cve.org/CVERecord?id=CVE-2025-4565 Référence CVE CVE-2025-4574 https://www.cve.org/CVERecord?id=CVE-2025-4574 Référence CVE CVE-2025-4598 https://www.cve.org/CVERecord?id=CVE-2025-4598 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-46701 https://www.cve.org/CVERecord?id=CVE-2025-46701 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-47183 https://www.cve.org/CVERecord?id=CVE-2025-47183 Référence CVE CVE-2025-47806 https://www.cve.org/CVERecord?id=CVE-2025

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

ord?id=CVE-2025-36442 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37958 https://www.cve.org/CVERecord?id=CVE-2025-37958 Référence CVE CVE-2025-38086 https://www.cve.org/CVERecord?id=CVE-2025-38086 Référence CVE CVE-2025-38089 https://www.cve.org/CVERecord?id=CVE-2025-38089 Référence CVE CVE-2025-38110 https://www.cve.org/CVERecord?id=CVE-2025-38110 Référence CVE CVE-2025-41248 https://www.cve.org/CVERecord?id=CVE-2025-41248 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-47935 https://www.cve.org/CVERecord?id=CVE-2025-47935 Référence CVE CVE-2025-47944 https://www.cve.org/CVERecord?id=CVE-2025-47944 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=CV

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

.org/CVERecord?id=CVE-2025-4056 Référence CVE CVE-2025-40909 https://www.cve.org/CVERecord?id=CVE-2025-40909 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-45768 https://www.cve.org/CVERecord?id=CVE-2025-45768 Référence CVE CVE-2025-4598 https://www.cve.org/CVERecord?id=CVE-2025-4598 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-20

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

ord?id=CVE-2025-40240 Référence CVE CVE-2025-40243 https://www.cve.org/CVERecord?id=CVE-2025-40243 Référence CVE CVE-2025-40244 https://www.cve.org/CVERecord?id=CVE-2025-40244 Référence CVE CVE-2025-40245 https://www.cve.org/CVERecord?id=CVE-2025-40245 Référence CVE CVE-2025-40346 https://www.cve.org/CVERecord?id=CVE-2025-40346 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-43857 https://www.cve.org/CVERecord?id=CVE-2025-43857 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4598 https://www.cve.org/CVERecord?id=CVE-2025-4598 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47219 https://www.cve.org/CVERecord?id=CVE-2025-47219 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-20

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

rg/CVERecord?id=CVE-2025-4287 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-43857 https://www.cve.org/CVERecord?id=CVE-2025-43857 Référence CVE CVE-2025-43859 https://www.cve.org/CVERecord?id=CVE-2025-43859 Référence CVE CVE-2025-43965 https://www.cve.org/CVERecord?id=CVE-2025-43965 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4565 https://www.cve.org/CVERecord?id=CVE-2025-4565 Référence CVE CVE-2025-45768 https://www.cve.org/CVERecord?id=CVE-2025-45768 Référence CVE CVE-2025-4598 https://www.cve.org/CVERecord?id=CVE-2025-4598 Référence CVE CVE-2025-46148 https://www.cve.org/CVERecord?id=CVE-2025-46148 Référence CVE CVE-2025-46149 https://www.cve.org/CVERecord?id=CVE-2025-46149 Référence CVE CVE-2025-46150 https://www.cve.org/CVERecord?id=CVE-2025-46150 Référence CVE CVE-2025-46152 https://www.cve.org/CVERecord?id=CVE-2025-46152 Référence CVE CVE-2025-46153 https://www.cve.org/CVERecord?id=CVE-

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

/CVERecord?id=CVE-2025-4091 Référence CVE CVE-2025-4092 https://www.cve.org/CVERecord?id=CVE-2025-4092 Référence CVE CVE-2025-4096 https://www.cve.org/CVERecord?id=CVE-2025-4096 Référence CVE CVE-2025-41232 https://www.cve.org/CVERecord?id=CVE-2025-41232 Référence CVE CVE-2025-41234 https://www.cve.org/CVERecord?id=CVE-2025-41234 Référence CVE CVE-2025-41242 https://www.cve.org/CVERecord?id=CVE-2025-41242 Référence CVE CVE-2025-4372 https://www.cve.org/CVERecord?id=CVE-2025-4372 Référence CVE CVE-2025-43857 https://www.cve.org/CVERecord?id=CVE-2025-43857 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-45768 https://www.cve.org/CVERecord?id=CVE-2025-45768 Référence CVE CVE-2025-4598 https://www.cve.org/CVERecord?id=CVE-2025-4598 Référence CVE CVE-2025-4609 https://www.cve.org/CVERecord?id=CVE-2025-4609 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-4664 https://www.cve.org/CVERecord?id=CVE-2025-4664 Référence CVE CVE-2025-46701 https://www.cve.org/CVERecord?id=CVE-2025-46701 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-009391GNU Project の GNU tar におけるパストラバーサルの脆弱性

GNU Project の GNU tar には、パストラバーサルの脆弱性が存在します。

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.
Patch available
Affected
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jul 2025 · Last source change 2 Nov 2025, 00:12 UTC · CWE-24 · Path Traversal: '../filedir'

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-2025-21178
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    tar.src as a component of Red Hat Enterprise Linux 6; tar.src as a component of Red Hat Enterprise Linux 7; tar as a component of Red Hat Enterprise Linux 8; tar.src as a component of Red Hat Enterprise Linux 8; io.syndesis-syndesis-ui as a component of Red Hat Fuse 7; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: tar-2:1.35-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.src as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); and 32 more
    After
    tar.src as a component of Red Hat Enterprise Linux 6; tar.src as a component of Red Hat Enterprise Linux 7; io.syndesis-syndesis-ui as a component of Red Hat Fuse 7; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: tar-2:1.35-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.src as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.30-13.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-2:1.30-13.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-2:1.30-13.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-2:1.30-13.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-2:1.30-13.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debuginfo-2:1.30-13.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debuginfo-2:1.30-13.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debuginfo-2:1.30-13.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debuginfo-2:1.30-13.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debugsource-2:1.30-13.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debugsource-2:1.30-13.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debugsource-2:1.30-13.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); tar-debugsource-2:1.30-13.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 45 more
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    ≤ 1.35 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    ≤ 1.35 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    tar.src as a component of Red Hat Enterprise Linux 6; tar.src as a component of Red Hat Enterprise Linux 7; tar as a component of Red Hat Enterprise Linux 8; tar.src as a component of Red Hat Enterprise Linux 8; io.syndesis-syndesis-ui as a component of Red Hat Fuse 7; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: tar-2:1.35-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.src as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); and 32 more
    After
    tar.src as a component of Red Hat Enterprise Linux 6; tar.src as a component of Red Hat Enterprise Linux 7; tar as a component of Red Hat Enterprise Linux 8; tar.src as a component of Red Hat Enterprise Linux 8; io.syndesis-syndesis-ui as a component of Red Hat Fuse 7; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: tar-2:1.35-7.el10_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-7.el10_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 10.0); tar-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.src as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debuginfo-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-debugsource-2:1.35-9.el10_1.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10); tar-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debuginfo-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); tar-debugsource-2:1.34-6.el9_4.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.9.4); and 32 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-21178↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Public exploit 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-2025-45582 · cve.blacktree.nl