Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.72% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-33195High confidence
Rails Active Storage has possible Path Traversal in DiskService
rails · activestorage
Official source article: GitHub GHSA-9XRJ-H377-FR87 ↗. Check the applicable product and release in the original source.
8.0HighCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs rails activestorage 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.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 17 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-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.
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 2 affected package states 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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | rails | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | rails | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | rails | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:7.2.3.1+dfsg-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | rails | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:7.2.3.1+dfsg-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | rails | 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 |
Open-source package ranges6 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 package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| RubyGemsactivestorage | ECOSYSTEM: introduced 8.1.0.beta1; fixed 8.1.2.1 | 8.1.2.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| RubyGemsactivestorage | ECOSYSTEM: introduced 8.0.0.beta1; fixed 8.0.4.1 | 8.0.4.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| RubyGemsactivestorage | ECOSYSTEM: introduced 0; fixed 7.2.3.1 | 7.2.3.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| rubygemsactivestorage | >= 8.1.0.beta1, < 8.1.2.1 | 8.1.2.1 | GitHub advisory ↗upstream repository advisory · 13 May 2026 |
| rubygemsactivestorage | >= 8.0.0.beta1, < 8.0.4.1 | 8.0.4.1 | GitHub advisory ↗upstream repository advisory · 13 May 2026 |
| rubygemsactivestorage | < 7.2.3.1 | 7.2.3.1 | GitHub advisory ↗upstream repository advisory · 13 May 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-2026-33195 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityRails: Active Storage: Active Storage (Rails): Arbitrary file access via path traversal in blob keys
The vendor explicitly identifies these products as affected by this CVE.
- 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel9 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp21/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp22/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2
- Summary
- A flaw was found in Active Storage, a component of Rails applications that manages file attachments. This vulnerability allows an attacker to manipulate file paths by using specially crafted input in blob keys. This manipulation can lead to unauthorized reading, writing, or deletion of arbitrary files on the server, potentially compromising the integrity and confidentiality of data.
- Remediation
- To mitigate this issue, ensure that blob keys used by Active Storage are not derived from untrusted user input. Applications should validate and sanitize any user-provided data before it is used in blob keys to prevent path traversal sequences.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Active Storage allows users to attach cloud and local files in Rails applications. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Storage's `DiskService#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
What
Active Storage allows users to attach cloud and local files in Rails applications. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Storage's `DiskService#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Active Storage allows users to attach cloud and local files in Rails applications. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Storage's `DiskService#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or 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 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
- a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-22 ↗
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
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
- 3scale-amp2/system-rhel7 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/system-rhel8 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/system-rhel9 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp2/zync-rhel9 as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp20/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp21/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp21/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp22/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp22/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp24/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp24/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp25/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp25/zync as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp26/system as a component of Red Hat 3scale API Management Platform 2
- 3scale-amp26/zync as a component of Red Hat 3scale API Management Platform 2
- 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
- To mitigate this issue, ensure that blob keys used by Active Storage are not derived from untrusted user input. Applications should validate and sanitize any user-provided data before it is used in blob keys to prevent path traversal sequences.
04
Evidence and provenance
Published 23 Mar 2026 · Last source change 19 Aug 2026, 12:05 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE recordCVE.org · 5.2
CVSS sourceCNA
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-2026-14632
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
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.