CVE-2025-49142

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-17714 (ENISA EUVD) · GHSA-wjw6-95h5-4jpx (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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: 0.4%CVSS: 7.1Exploit: 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 prior to 2.4.10 or prior to 1.6.32 are potentially affected. Due to insufficient security configuration of the Jinja2 templating feature used in computed fields, custom links, etc. in Nautobot, a malicious user could configure this feature set in ways that could expose the value of Secrets defined in Nautobot when the templated content is rendered or that could call Python APIs to modify data within Nautobot when the templated content is rendered, bypassing the object permissions assigned to the viewing user. Nautobot versions 1.6.32 and 2.4.10 will include fixes for the vulnerability. The vulnerability can be partially mitigated by configuring object permissions appropriately to limit certain actions to only trusted users.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
0.4%
EPSS %ILE
31st
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

June 10, 2025

Last Modified

August 21, 2025

Advisory Details (5)

Auto-updated Oct 25, 2026
Patch available. Sources: github_pr, github.
Web page

Sandbox — Jinja Documentation (3.1.x)

https://jinja.palletsprojects.com/en/stable/sandbox
GitHub advisoryMentions a patch (unverified)

Secrets exposure and data manipulation through Jinja2 templating · Advisory · nautobot/nautobot · GitHub

https://github.com/nautobot/nautobot/security/advisories/GHSA-wjw6-95h5-4jpx
GitHub pull request

[1.6] Add @unsafe, .alters_data, and/or .do_not_call_in_templates as applicable

Fix merged in nautobot/nautobot PR #7429 on 2025-06-09 — awaiting tagged release

https://github.com/nautobot/nautobot/pull/7429
GitHub pull request

Add `@unsafe`, `.alters_data`, and/or `.do_not_call_in_templates` to various model methods

Fix merged in nautobot/nautobot PR #7417 on 2025-06-06 — awaiting tagged release

https://github.com/nautobot/nautobot/pull/7417
Web page

The Django template language: for Python programmers | Django documentation | Django

https://docs.djangoproject.com/en/4.2/ref/templates/api/#alters-data-description

Vendor Advisories for CVE-2025-49142(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipnautobot @ 1.6.32 (fixes < 1.6.32)—ghsa
pipnautobot @ 2.4.10 (fixes >= 2.0.0, < 2.4.10)—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

(2 across 1 ecosystem)
PyPI(2)
PackageVulnerable rangeFix by version rangeDependents
jinja2———
nautobot1.0.0 ... 2.4.9 (166 versions)
  • every version up to 1.6.32: fixed in 1.6.32
  • 2.0.0 up to 2.4.10: fixed in 2.4.10
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 95 of 220 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-49142?
CVE-2025-49142 is a high-severity vulnerability; its CVE record was published on June 10, 2025. Nautobot is a Network Source of Truth and Network Automation Platform. All users of Nautobot versions prior to 2.4.10 or prior to 1.6.32 are potentially affected. Due to insufficient security configuration of the Jinja2 templating feature used in computed fields, custom links, etc. in Nautobot, a…
When was the CVE record for CVE-2025-49142 published?
The CVE record for CVE-2025-49142 was published on June 10, 2025. 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 August 21, 2025; the record at its source may have been updated since.
Is CVE-2025-49142 actively exploited?
CVE-2025-49142 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-49142?
CVE-2025-49142 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-49142?
A fix for CVE-2025-49142 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-49142 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49142

Explore →

Is Your Infrastructure Affected by CVE-2025-49142?

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

Book a Demo →Browse All CVEs