CVE-2026-58174

Hermes WebUI before 0.51.521 validates the workspace of an imported session under the active named profile but constructs the Session object without setting its profile in the /api/session/import handler, so the imported session is persisted with a null profile. Because a null profile is treated as the default profile by the profile authorization check, a user on the default profile can export the imported session transcript and use its session identifier to read files from the named profile's workspace, defeating the application's profile isolation.

CVSS 4.0

6.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

0.5% chance of exploitation in the next 30 days; higher than 38% of CVEs (scores of 2026-10-25)

CWE

CWE-732

Published

2026-06-30

Modified

2026-10-25

Record from

the NVD, synced 2026-10-25

References

• https://github.com/nesquena/hermes-webui/commit/3d5ef4758e920ba6888d49aaa4341de214693496
• https://github.com/nesquena/hermes-webui/pull/4489
• https://github.com/nesquena/hermes-webui/pull/4506
• https://github.com/nesquena/hermes-webui/releases/tag/v0.51.521
• https://www.vulncheck.com/advisories/hermes-webui-cross-profile-authorization-bypass-via-unset-session-profile-on-import

Check your stackJSON