CVE-2026-71210

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-08-05. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

Mealie's AsyncSafeTransport SSRF guard (mealie/pkgs/safehttp/transport.py) resolves a target hostname once, checks the resolved IP against private-range rules, but then issues the actual outbound HTTP request using the original hostname, which the underlying async transport re-resolves independently.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

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

GitHub - mealie-recipes/mealie: Mealie is a self hosted recipe manager and meal planner with a RestAPI backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family. Easily add recipes into your database by providing the url and mealie will automatically import the relevant data or add a family recipe with the UI editor · GitHub

https://github.com/mealie-recipes/mealie

Vendor Advisories for CVE-2026-71210(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 23× in last 7d / 59× 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-21 06:28 UTCEG score recompute
  2. 2026-08-21 06:28 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 04:45 UTCEG score recompute
  5. 2026-08-20 04:45 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 03:01 UTCEG score recompute
  8. 2026-08-19 03:01 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 00:58 UTCEG score recompute
  12. 2026-08-18 00:58 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 22:49 UTCEG score recompute
  15. 2026-08-16 22:49 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 21:06 UTCEG score recompute
  20. 2026-08-15 21:06 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 19:23 UTCEG score recompute
  23. 2026-08-14 19:23 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 17:39 UTCGHSA enrichment
Show 34 more
  1. 2026-08-12 15:51 UTCEG score recompute
  2. 2026-08-12 15:51 UTCGHSA enrichment
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 14:08 UTCEG score recompute
  5. 2026-08-11 14:08 UTCGHSA enrichment
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 12:25 UTCEG score recompute
  8. 2026-08-10 12:25 UTCGHSA enrichment
  9. 2026-08-10 12:02 UTCGHSA enrichment
  10. 2026-08-10 11:22 UTCEG score recompute
  11. 2026-08-10 11:22 UTCGHSA enrichment
  12. 2026-08-09 21:20 UTCEG score recompute
  13. 2026-08-09 21:20 UTCGHSA enrichment
  14. 2026-08-09 13:47 UTCEPSS rescore
  15. 2026-08-08 19:37 UTCEG score recompute
  16. 2026-08-08 19:37 UTCGHSA enrichment
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-07 17:54 UTCEG score recompute
  19. 2026-08-07 17:54 UTCGHSA enrichment
  20. 2026-08-06 16:10 UTCEG score recompute
  21. 2026-08-06 16:10 UTCGHSA enrichment
  22. 2026-08-06 13:47 UTCEPSS rescore
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-05 19:17 UTCEPSS rescore
  25. 2026-08-05 14:27 UTCEG score recompute
  26. 2026-08-05 14:27 UTCGHSA enrichment
  27. 2026-08-05 13:47 UTCEG score recompute
  28. 2026-08-05 13:47 UTCGHSA enrichment
  29. 2026-08-05 13:10 UTCEG score recompute
  30. 2026-08-05 13:09 UTCGHSA enrichment
  31. 2026-08-05 08:20 UTCEG score recompute 1.20
  32. 2026-08-05 08:20 UTCNVD updateCVSS v3 → 5.3
  33. 2026-08-05 07:22 UTCEG score recompute
  34. 2026-08-05 07:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71210?
CVE-2026-71210 is a medium vulnerability published on August 5, 2026. Mealie's AsyncSafeTransport SSRF guard (mealie/pkgs/safehttp/transport.py) resolves a target hostname once, checks the resolved IP against private-range rules, but then issues the actual outbound HTTP request using the original hostname, which the underlying async transport re-resolves…
When was CVE-2026-71210 disclosed?
CVE-2026-71210 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-71210 actively exploited?
CVE-2026-71210 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-71210?
CVE-2026-71210 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-71210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71210, 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-71210

Explore →

Is Your Infrastructure Affected by CVE-2026-71210?

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