Open Redirect in org.hswebframework.web:hsweb-authorization-oauth2 (CVE-2026-11477)
Summary
Vulnerability in org.hswebframework.web:hsweb-authorization-oauth2 (CVE-2026-11477). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was detected in hs-web hsweb-framework up to 5.0.1. This affects the function OAuth2Client of the file hsweb-authorization/hsweb-authorization-oauth2/src/main/java/org/hswebframework/web/oauth2/server/OAuth2Client.java of the component OAuth2 Client. The manipulation results in open redirect. The attack can be executed remotely. The exploit is now public and may be used. The patch is identified as c2882679a9125cea52678151af5ae213cbd52579. Applying a patch is advised to resolve this issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-11477 has been found in org.hswebframework.web:hsweb-authorization-oauth2.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.hswebframework.web:hsweb-authorization-oauth2 CVE-2026-11477" on the vendor's site.
CVE-2026-11477 (org.hswebframework.web:hsweb-authorization-oauth2) — CWE-601 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in org.hswebframework.web:hsweb-authorization-oauth2.
Check the vendor advisory for the affected versions of org.hswebframework.web:hsweb-authorization-oauth2.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.hswebframework.web:hsweb-authorization-oauth2 を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com