How many CVEs have patched set_provider_key?

1 published CVEs changed set_provider_key in nesquena/hermes-webui, in 2 distinct patches totalling 4 changed lines, between 2026 and 2026.

What is the latest CVE that changed set_provider_key?

CVE-2026-49955 (Hermes WebUI < 0.51.270 Resource Exhaustion via passkey/options), published 2026-06-09, changed lines 2096 to 2100 of api/providers.py.

How does set_provider_key compare to the rest of nesquena/hermes-webui?

nesquena/hermes-webui has 19 CVEs with a located fix in total; 1 of them changed set_provider_key.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

nesquena/hermes-webui

Function

set_provider_key

Name: set_provider_key in nesquena/hermes-webui: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

api/providers.py

Last patched June 9, 2026

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

4

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

set_provider_key in nesquena/hermes-webui was changed by 1 published CVE fixes in 2026, in 2 distinct patches that added or removed 4 lines in total.

nesquena/hermes-webui has 19 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed set_provider_key, newest first, with the lines each fix touched.

Hermes WebUI < 0.51.270 Resource Exhaustion via passkey/options
CVE-2026-49955 · lines 2096–2100 · +2 −2
Medium · CVSS 6.9
EPSS 0.8%2026-06-09

Get an alert when the next CVE fix lands in nesquena/hermes-webui, with the patched functions.

Monitor hermes-webui CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in nesquena/hermes-webui changed by the most CVE fixes.

handle_get4 CVEs · api/routes.py handle_post4 CVEs · api/routes.py _sync_session_title_to_insights3 CVEs · api/routes.py _llm_update_summary2 CVEs · api/routes.py _handle_session_import2 CVEs · api/routes.py _visible_pinned_lineage_ids2 CVEs · api/routes.py

All patched functions in nesquena/hermes-webui

Frequently asked questions

Common questions about CVE fixes to set_provider_key.

How many CVEs have patched set_provider_key?: 1 published CVEs changed set_provider_key in nesquena/hermes-webui, in 2 distinct patches totalling 4 changed lines, between 2026 and 2026.
What is the latest CVE that changed set_provider_key?: CVE-2026-49955 (Hermes WebUI < 0.51.270 Resource Exhaustion via passkey/options), published 2026-06-09, changed lines 2096 to 2100 of api/providers.py.
How does set_provider_key compare to the rest of nesquena/hermes-webui?: nesquena/hermes-webui has 19 CVEs with a located fix in total; 1 of them changed set_provider_key.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track nesquena/hermes-webui CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing