# CVE-2024-26143: Rails Possible XSS Vulnerability in Action Controller

> Attackers can inject malicious scripts via translation helpers in Rails controllers if specific unsafe patterns are used, requiring an upgrade to patched versions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Feb 2024
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-rails-2024-26143, GHSA-9822-6m93-xqf4, UBUNTU-CVE-2024-26143

## What is CVE-2024-26143?

CVE-2024-26143 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Rails is a web-application framework. There is a possible XSS vulnerability when using the translation helpers in Action Controller. Applications using translation methods like translate, or t on a controller, with a key ending in "_html", a :default key which contains untrusted user input, and the resulting string is used in a view, may be susceptible to an XSS vulnerability. The vulnerability is fixed in 7.1.3.1 and 7.0.8.1.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-26143?

9 open source packages ship an affected version, including rails and actionpack. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rails` | Bitnami | From 7.0.0 | 7.0.9, 7.1.4 |
| `rails` | RubyGems | From 7.0.0 | 7.0.8.1 |
| `rails` | RubyGems | From 7.0.0 | 7.0.8.1 |
| `rails` | RubyGems | From 7.1.0 | 7.1.3.1 |
| `rails` | RubyGems | From 7.1.0 | 7.1.3.1 |
| `actionpack` | RubyGems | From 7.0.0 | 7.0.8.1 |
| `actionpack` | RubyGems | From 7.0.0 | 7.0.8.1 |
| `actionpack` | RubyGems | From 7.1.0 | 7.1.3.1 |
| `actionpack` | RubyGems | From 7.1.0 | 7.1.3.1 |

Products: Rubyonrails Rails.

## How do I fix CVE-2024-26143?

Upgrade rails to a fixed version for your release line: 7.0.9, 7.1.4, 7.0.8.1 or 7.1.3.1.

## Is CVE-2024-26143 being exploited?

There is no known exploitation of CVE-2024-26143 in the wild and no public exploit code.

## Other vulnerabilities in Rubyonrails Rails

- [CVE-2013-0277](https://insights.sbomify.com/CVE-2013-0277/): Active Record contains deserialization of arbitrary YAML (critical 10.0)
- [CVE-2017-17916](https://insights.sbomify.com/CVE-2017-17916/): SQL injection in n/a (high 8.1)
- [CVE-2017-17917](https://insights.sbomify.com/CVE-2017-17917/): SQL injection in n/a (high 8.1)
- [CVE-2026-33195](https://insights.sbomify.com/CVE-2026-33195/): Rails Active Storage has possible Path Traversal in DiskService (high 8.0)
- [CVE-2024-26142](https://insights.sbomify.com/CVE-2024-26142/): Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26143 and fix it if it is affected.

What it is: CVE-2024-26143 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-26143 in the wild and no public exploit code.

Affected packages and fixed versions:
- rails (Bitnami): affected from 7.0.0; fixed in 7.0.9, 7.1.4
- rails (RubyGems): affected from 7.0.0; fixed in 7.0.8.1
- rails (RubyGems): affected from 7.0.0; fixed in 7.0.8.1
- rails (RubyGems): affected from 7.1.0; fixed in 7.1.3.1
- rails (RubyGems): affected from 7.1.0; fixed in 7.1.3.1
- actionpack (RubyGems): affected from 7.0.0; fixed in 7.0.8.1
- actionpack (RubyGems): affected from 7.0.0; fixed in 7.0.8.1
- actionpack (RubyGems): affected from 7.1.0; fixed in 7.1.3.1
- actionpack (RubyGems): affected from 7.1.0; fixed in 7.1.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26143/ (Markdown: https://insights.sbomify.com/CVE-2024-26143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26143
- OSV: https://osv.dev/vulnerability/CVE-2024-26143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26143/
Summaries are generated and may contain mistakes; the official description above is the record.