Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.27% for the current model date.
BlackTreeCVE IntelligenceRails · ActiveSupport
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
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 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:7.2.2.1+dfsg-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | rails | Vendor fix publishedDebian records a fixed source-package version for this release. | 2:6.1.7.10+dfsg-1~deb12u1 | 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.2.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.2.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 |
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 |
|---|---|---|---|
| RubyGemsactivesupport | ECOSYSTEM: introduced 5.2.0; fixed 6.1.7.5 | 6.1.7.5 | OSV record ↗aggregator derived · 10 Sep 2026 |
| RubyGemsactivesupport | ECOSYSTEM: introduced 7.0.0; fixed 7.0.7.1 | 7.0.7.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| rubygemsactivesupport | >= 5.2.0, < 6.1.7.5 | 6.1.7.5 | GitHub advisory ↗github reviewed aggregator · 18 Feb 2025 |
| rubygemsactivesupport | >= 7.0.0, < 7.0.7.1 | 7.0.7.1 | GitHub advisory ↗github reviewed aggregator · 18 Feb 2025 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch availableActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file's permissions are defaulted to the user's current `umask` settings, meaning that it's possible for other users on the same system to read the contents of the temporary file. Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it. All users running an affected release should either upgrade or use one of the workarounds immediately.
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file's permissions are defaulted to the user's current `umask` settings, meaning that it's possible for other users on the same system to read the contents of the temporary file. Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it. All users running an affected release should either upgrade or use one of the workarounds immediately.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
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.
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file's permissions are defaulted to the user's current `umask` settings, meaning that it's possible for other users on the same system to read the contents of the temporary file. Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it. All users running an affected release should either upgrade or use one of the workarounds immediately.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
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.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-732: Incorrect Permission Assignment for Critical Resource. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:LCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 9 Jan 2025 · Last source change 15 Feb 2025, 00:10 UTC · CWE-732 · Incorrect Permission Assignment for Critical Resource
Core structured fields are present and their contributing authorities are shown above.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.