🛡️ CVE-2026-71282

🟡 CVSS 6.5 — Medium ✅ No Known Exploit CWE-89 NVD
6.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

ChirpStack's SQLite-backend device tag filtering (chirpstack/src/storage/device.rs, in both get_count and list) interpolates the user-supplied tag KEY directly into a raw SQL fragment via Rust's format! macro , while only the tag VALUE is safely parameter-bound via Diesel's .bind.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

Weakness class

CVE-2026-71282 is classified as CWE-89: SQL Injection. Untrusted input is concatenated into an SQL statement, letting an attacker change the query and reach data the request should not return.

Affected software

CVE-2026-71282 is recorded against 1 package.

  • unknown

Timeline and source

Published on 5 August 2026 and last revised on 10 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com
github.com

Details

Severity MEDIUM
CVSS Score 6.5
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CWE CWE-89
Public Exploit ✅ No
Source NVD
Published 2026-08-05
Updated 2026-08-11
Modified 2026-08-10
Fix URL N/A

Affected Packages

Software From version Fixed in
unknown — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in the affected software

CVE-2026-71282 is rated CVSS 6.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.