Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.24% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2025-22873High confidence
Improper access to parent directory of root in os
Go standard library · os
3.8LowCVSS 3.1
Scheduled
Patch availableLow technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityLow→Operational priority:Low, unchanged from published severity.unchanged
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
- Confirm that the asset runs Go standard library os and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
6 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.24.3-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.24.3-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.21v3.21 · community | go | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.23.9-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Debian trixietrixie · source | golang-1.24 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.24.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | golang-1.19 | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | golang-1.24 | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative 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.
CVE-2025-22873 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityos: os: Information disclosure via path traversal using specially crafted filenames
The vendor explicitly identifies these products as affected by this CVE.
- rhai/assisted-installer-rhel9 as a component of Assisted Installer for Red Hat OpenShift Container Platform 2
- openshift-builds/openshift-builds-waiters-rhel9 as a component of Builds for Red Hat OpenShift
- cert-manager/jetstack-cert-manager-rhel9 as a component of cert-manager Operator for Red Hat OpenShift
- compliance/openshift-compliance-operator-bundle as a component of Compliance Operator
- build-of-trustee/trustee-rhel9-operator as a component of Confidential Compute Attestation
- openshift-sandboxed-containers/osc-monitor-rhel9 as a component of Confidential Compute Attestation
- cryostat/cryostat-storage-rhel9 as a component of Cryostat 4
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator
- external-secrets-operator/external-secrets-rhel9 as a component of External Secrets Operator for Red Hat OpenShift
- edo/external-dns-rhel8 as a component of ExternalDNS Operator
- edo/external-dns-rhel9 as a component of ExternalDNS Operator
- Summary
- A path traversal vulnerability has been identified in the Go os package affecting the Root abstraction, where improper handling of trailing path separators could allow access to the parent directory of a configured root directory. By supplying a filename ending in "../", an attacker may be able to open the immediate parent directory of the intended Root. Although this escape does not allow traversal to higher-level ancestors or direct access to files within the parent directory, it may expose directory metadata or unintended filesystem structure if the application passes untrusted path input to Root.Open.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". For example, Root.Open("../") would open the parent directory of the Root. This escape only permits opening the parent directory itself, not ancestors of the parent or files contained within the parent.
What
It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". For example, Root.Open("../") would open the parent directory of the Root. This escape only permits opening the parent directory itself, not ancestors of the parent or files contained within the parent.
Why
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as .. that can resolve to a location that is outside of that directory.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". For example, Root.Open("../") would open the parent directory of the Root. This escape only permits opening the parent directory itself, not ancestors of the parent or files contained within the parent.
Why
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as .. that can resolve to a location that is outside of that directory.
How
An attacker operating through local access may attempt exploitation with low privileges. 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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Relative Path Traversal → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-23 ↗
CWE-23: Relative Path Traversal. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as .. 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:L/PR:L/UI:N/S:C/C:L/I:N/A:NCommon 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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- 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.
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
- rhai/assisted-installer-rhel9 as a component of Assisted Installer for Red Hat OpenShift Container Platform 2
- openshift-builds/openshift-builds-waiters-rhel9 as a component of Builds for Red Hat OpenShift
- cert-manager/jetstack-cert-manager-rhel9 as a component of cert-manager Operator for Red Hat OpenShift
- compliance/openshift-compliance-operator-bundle as a component of Compliance Operator
- build-of-trustee/trustee-rhel9-operator as a component of Confidential Compute Attestation
- openshift-sandboxed-containers/osc-monitor-rhel9 as a component of Confidential Compute Attestation
- cryostat/cryostat-storage-rhel9 as a component of Cryostat 4
- custom-metrics-autoscaler/custom-metrics-autoscaler-rhel9 as a component of Custom Metric Autoscaler operator for Red Hat Openshift
- dvo/deployment-validation-rhel8-operator as a component of Deployment Validation Operator
- external-secrets-operator/external-secrets-rhel9 as a component of External Secrets Operator for Red Hat OpenShift
- edo/external-dns-rhel8 as a component of ExternalDNS Operator
- edo/external-dns-rhel9 as a component of ExternalDNS Operator
- workload-availability/fence-agents-remediation-rhel8-operator as a component of Fence Agents Remediation Operator
- compliance/openshift-compliance-operator-bundle as a component of File Integrity Operator
- gatekeeper/gatekeeper-rhel9-operator as a component of Gatekeeper 3
- openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- openshift-logging/logging-loki-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
- lvms4/lvms-rhel9-operator as a component of Logical Volume Manager Storage
- lvms4/topolvm-rhel8 as a component of Logical Volume Manager Storage
- lvms4/topolvm-rhel9 as a component of Logical Volume Manager Storage
- workload-availability/machine-deletion-remediation-rhel8-operator as a component of Machine Deletion Remediation Operator
- mta/mta-cli-rhel9 as a component of Migration Toolkit for Applications 8
- rhmtc/openshift-migration-registry-rhel8 as a component of Migration Toolkit for Containers
- openshift/mirror-registry-rhel8 as a component of mirror registry for Red Hat OpenShift
- openshift/mirror-registry-rhel8 as a component of mirror registry for Red Hat OpenShift 2
- multiarch-tuning/multiarch-tuning-rhel9-operator as a component of Multiarch Tuning Operator
- multicluster-engine/discovery-rhel9 as a component of Multicluster Engine for Kubernetes
- multicluster-globalhub/multicluster-globalhub-agent-rhel9 as a component of Multicluster Global Hub
- network-observability/network-observability-cli-rhel9 as a component of Network Observability Operator
- workload-availability/node-healthcheck-rhel8-operator as a component of Node HealthCheck Operator
- and 215 more
- Fixed
- golang1-25-main@aarch64 as a component of Red Hat Hardened Images
- golang1-25-main@noarch as a component of Red Hat Hardened Images
- golang1-25-main@src as a component of Red Hat Hardened Images
- golang1-25-main@x86_64 as a component of Red Hat Hardened Images
- golang1-26-main@aarch64 as a component of Red Hat Hardened Images
- golang1-26-main@noarch as a component of Red Hat Hardened Images
- golang1-26-main@src as a component of Red Hat Hardened Images
- golang1-26-main@x86_64 as a component of Red Hat Hardened Images
- Action
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- [security] Go 1.24.3 and Go 1.23.9 are released →Original publisher ↗Searchable text snapshot · Captured 28 Sep 2026Groups Groups Conversations All groups and messages Send feedback to Google Help Training Sign in Groups Groups Conversations About [security] Go 1.24.3 and Go 1.23.9 are released 3,388 views Skip to first unread message Cherry Mui unread, May 6, 2025, 8:49:48 PM 5/6/25 Reply to author Sign
04
Evidence and provenance
Published 4 Feb 2026 · Last source change 5 Feb 2026, 15:03 UTC · CWE-23 · Relative Path Traversal
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-206863
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
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 1.23.9; 1.24.0-0 < 1.24.3 · 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.
- After
- < 1.23.9; 1.24.0-0 < 1.24.3 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
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.