CVE-2026-71276

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Magistrala (formerly Mainflux)'s message-readers API reads a value from the HTTP query string (readers/api/http/transport.go) with no validation and interpolates it directly into raw SQL queries via fmt.Sprintf in both the PostgreSQL reader (readers/postgres/messages.go: ) and the TimescaleDB reader (readers/timescale/messages.go, same pattern), enabling SQL injection by any authenticated user able to query channel messages.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

magistrala/readers/postgres/messages.go at main · absmach/magistrala · GitHub

https://github.com/absmach/magistrala/blob/main/readers/postgres/messages.go
generic

GitHub - absmach/magistrala: IoT Platform Framework · GitHub

https://github.com/absmach/magistrala

Vendor Advisories for CVE-2026-71276(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 07:08 UTCGHSA enrichment
  2. 2026-08-19 18:53 UTCEG score recompute
  3. 2026-08-19 18:53 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 06:30 UTCGHSA enrichment
  6. 2026-08-18 18:14 UTCEG score recompute
  7. 2026-08-18 18:14 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 04:19 UTCGHSA enrichment
  11. 2026-08-17 16:01 UTCEG score recompute
  12. 2026-08-17 16:01 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 03:46 UTCGHSA enrichment
  15. 2026-08-16 15:30 UTCEG score recompute
  16. 2026-08-16 15:30 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 03:15 UTCEG score recompute
  20. 2026-08-16 03:15 UTCGHSA enrichment
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 15:00 UTCGHSA enrichment
  23. 2026-08-15 02:44 UTCEG score recompute
  24. 2026-08-15 02:44 UTCGHSA enrichment
  25. 2026-08-15 01:31 UTCEPSS rescore
Show 43 more
  1. 2026-08-14 14:29 UTCGHSA enrichment
  2. 2026-08-14 02:13 UTCEG score recompute
  3. 2026-08-14 02:13 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 13:58 UTCGHSA enrichment
  6. 2026-08-13 01:42 UTCEG score recompute
  7. 2026-08-13 01:42 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 13:27 UTCGHSA enrichment
  10. 2026-08-12 01:09 UTCEG score recompute
  11. 2026-08-12 01:09 UTCGHSA enrichment
  12. 2026-08-11 12:54 UTCGHSA enrichment
  13. 2026-08-11 00:39 UTCEG score recompute
  14. 2026-08-11 00:39 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 12:24 UTCEG score recompute
  17. 2026-08-10 12:24 UTCGHSA enrichment
  18. 2026-08-10 11:42 UTCGHSA enrichment
  19. 2026-08-10 11:22 UTCEG score recompute
  20. 2026-08-10 11:22 UTCGHSA enrichment
  21. 2026-08-10 06:47 UTCGHSA enrichment
  22. 2026-08-09 18:32 UTCEG score recompute
  23. 2026-08-09 18:32 UTCGHSA enrichment
  24. 2026-08-09 13:47 UTCEPSS rescore
  25. 2026-08-09 06:17 UTCGHSA enrichment
  26. 2026-08-08 18:01 UTCEG score recompute
  27. 2026-08-08 18:01 UTCGHSA enrichment
  28. 2026-08-08 16:37 UTCEPSS rescore
  29. 2026-08-08 05:45 UTCGHSA enrichment
  30. 2026-08-07 17:30 UTCEG score recompute
  31. 2026-08-07 17:30 UTCGHSA enrichment
  32. 2026-08-07 05:15 UTCGHSA enrichment
  33. 2026-08-06 17:00 UTCEG score recompute
  34. 2026-08-06 17:00 UTCGHSA enrichment
  35. 2026-08-06 13:47 UTCEPSS rescore
  36. 2026-08-06 04:44 UTCGHSA enrichment
  37. 2026-08-05 16:29 UTCEG score recompute
  38. 2026-08-05 16:29 UTCGHSA enrichment
  39. 2026-08-05 16:13 UTCEG score recompute
  40. 2026-08-05 16:13 UTCGHSA enrichment
  41. 2026-08-05 13:27 UTCEG score recompute
  42. 2026-08-05 13:07 UTCEG score recompute
  43. 2026-08-05 13:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71276?
CVE-2026-71276 is a high vulnerability published on August 5, 2026. Magistrala (formerly Mainflux)'s message-readers API reads a value from the HTTP query string (readers/api/http/transport.go) with no validation and interpolates it directly into raw SQL queries via fmt.Sprintf in both the PostgreSQL reader (readers/postgres/messages.go: ) and the TimescaleDB…
When was CVE-2026-71276 disclosed?
CVE-2026-71276 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71276 actively exploited?
CVE-2026-71276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.9% of all scored CVEs.
What is the CVSS score of CVE-2026-71276?
CVE-2026-71276 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-71276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71276, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71276

Explore →

Is Your Infrastructure Affected by CVE-2026-71276?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.