LibreTranslate up to 1.9.7 X-Forwarded-For get_remote_address less trusted source
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 1.21 |
Summary
A vulnerability was found in LibreTranslate up to 1.9.7. It has been rated as problematic. Affected by this issue is the function get_remote_address of the component X-Forwarded-For Handler. Performing a manipulation results in less trusted source.
This vulnerability is identified as CVE-2026-57942. The attack can be initiated remotely. There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in LibreTranslate up to 1.9.7. This affects the function get_remote_address of the component X-Forwarded-For Handler. The manipulation with an unknown input leads to a less trusted source vulnerability. CWE is classifying the issue as CWE-348. The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack. This is going to have an impact on availability. The summary by CVE is:
LibreTranslate through 1.9.7, fixed in commit 397fd22, contains an IP spoofing vulnerability in the get_remote_address() function that allows unauthenticated attackers to spoof client IP addresses by injecting arbitrary values into the X-Forwarded-For header without trusted proxy validation. Attackers can bypass per-IP rate limiting and flood bans by supplying forged addresses in the X-Forwarded-For header to enable unlimited API abuse.
The weakness was released by George Chen as 986. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-57942 since 06/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Applying the patch 397fd224080515d4001a1bc60c8fed53e3c56b6f is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-40160). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Less trusted sourceCWE: CWE-348
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 397fd224080515d4001a1bc60c8fed53e3c56b6f
Timeline
06/26/2026 CVE reserved06/29/2026 Advisory disclosed
06/29/2026 VulDB entry created
06/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 986
Researcher: George Chen
Status: Confirmed
CVE: CVE-2026-57942 (🔒)
GCVE (CVE): GCVE-0-2026-57942
GCVE (VulDB): GCVE-100-374661
EUVD: 🔒
Entry
Created: 06/29/2026 20:30Updated: 06/29/2026 23:04
Changes: 06/29/2026 20:30 (78), 06/29/2026 23:04 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.