CVE-2023-25657

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-02-22. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-0178 (ENISA EUVD) · GHSA-8mfq-f5wj-vw5m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions earlier than 1.5.7 are impacted by a remote code execution vulnerability. Nautobot did not properly sandbox Jinja2 template rendering. In Nautobot 1.5.7 has enabled sandboxed environments for the Jinja2 template engine used internally for template rendering for the following objects: extras.ComputedField, extras.CustomLink, extras.ExportTemplate, extras.Secret, extras.Webhook. While no active exploits of this vulnerability are known this change has been made as a preventative measure to protect against any potential remote code execution attacks utilizing maliciously crafted template code. This change forces the Jinja2 template engine to use a SandboxedEnvironment on all new installations of Nautobot. This addresses any potential unsafe code execution everywhere the helper function nautobot.utilities.utils.render_jinja2 is called. Additionally, the documentation that had previously suggesting the direct use of jinja2.Template has been revised to suggest render_jinja2. Users are advised to upgrade to Nautobot 1.5.7 or newer. For users that are unable to upgrade to the latest release of Nautobot, you may add the following setting to your nautobot_config.py to apply the sandbox environment enforcement: TEMPLATES[1]["OPTIONS"]["environment"] = "jinja2.sandbox.SandboxedEnvironment" After applying this change, you must restart all Nautobot services, including any Celery worker processes. Note: *Nautobot specifies two template engines by default, the first being “django” for the Django built-in template engine, and the second being “jinja” for the Jinja2 template engine. This recommended setting will update the second item in the list of template engines, which is the Jinja2 engine.* For users that are unable to immediately update their configuration such as if a Nautobot service restart is too disruptive to operations, access to provide custom Jinja2 template values may be mitigated using permissions to restrict “change” (write) actions to the affected object types listed in the first section. Note: *This solution is intended to be stopgap until you can successfully update your nautobot_config.py or upgrade your Nautobot instance to apply the sandboxed environment enforcement.*

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.5%
EPSS %ILE
74th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 21, 2023

Last Modified

November 21, 2024

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipnautobot @ 1.5.7 (fixes < 1.5.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nautobot1.0.0 ... 1.5.6 (67 versions)
  • every version up to 1.5.7: fixed in 1.5.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 209 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:39 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  3. 2026-11-01 08:22 UTCGHSA enrichmentGHSA-8mfq-f5wj-vw5m · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-01 08:22 UTCEG score recompute
  5. 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  6. 2026-10-30 16:31 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  7. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  9. 2026-10-28 06:00 UTCEG score recompute
  10. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  11. 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  12. 2026-10-25 17:46 UTCEG score recompute
  13. 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  14. 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  16. 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  17. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  18. 2026-10-21 04:44 UTCEG score recompute
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  21. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  22. 2026-10-18 08:10 UTCEG score recompute
  23. 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  24. 2026-10-16 16:35 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  25. 2026-10-15 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
Show 73 more
  1. 2026-10-14 20:24 UTCOSV refresh
  2. 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  3. 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.5% · 74th percentile
  4. 2026-10-12 18:33 UTCEG score recompute
  5. 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  6. 2026-10-11 21:57 UTCEG score recompute
  7. 2026-10-11 13:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  8. 2026-10-10 19:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  10. 2026-10-08 17:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  11. 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  12. 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  13. 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  14. 2026-10-04 23:19 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  16. 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  17. 2026-10-01 19:47 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  18. 2026-09-30 16:19 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  20. 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  21. 2026-09-26 15:55 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  22. 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  24. 2026-09-23 19:41 UTCOSV refresh
  25. 2026-09-23 13:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  26. 2026-09-22 14:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  27. 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  28. 2026-09-18 19:25 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  29. 2026-09-17 19:24 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  30. 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  31. 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  32. 2026-09-15 03:07 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  33. 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  34. 2026-09-12 14:58 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  35. 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  36. 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  37. 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  38. 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
  39. 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  40. 2026-09-04 14:29 UTCOSV refresh
  41. 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  42. 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  43. 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  44. 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  45. 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  46. 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  47. 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  48. 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  49. 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  50. 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  51. 2026-08-24 14:14 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  52. 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  53. 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  54. 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  55. 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  57. 2026-08-18 01:45 UTCOSV refresh
  58. 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  59. 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  60. 2026-08-16 02:12 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  61. 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  62. 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  63. 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  64. 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  65. 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  66. 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  67. 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  68. 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  69. 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  70. 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  71. 2026-08-03 10:34 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  72. 2026-08-02 20:57 UTCOSV refresh
  73. 2026-08-02 02:24 UTCEPSS rescoreEPSS 1.5% · 72nd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2023-25657?
CVE-2023-25657 is a high-severity vulnerability; its CVE record was published on February 21, 2023. Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions earlier than 1.5.7 are impacted by a remote code execution vulnerability. Nautobot did not properly sandbox Jinja2 template rendering. In Nautobot 1.5.7 has enabled sandboxed environments for the…
When was the CVE record for CVE-2023-25657 published?
The CVE record for CVE-2023-25657 was published on February 21, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-25657 actively exploited?
CVE-2023-25657 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-25657?
CVE-2023-25657 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2023-25657?
A fix for CVE-2023-25657 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-25657

Explore →

Is Your Infrastructure Affected by CVE-2023-25657?

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

Book a Demo →Browse All CVEs