sing-box vulnerable to improper authentication in the SOCKS inbound
CVE-2023-43644GHSA-r5hm-mp3j-285g
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/sagernet/sing-box 1.5.0-rc.5, 1.4.5; github.com/sagernet/sing 0.2.12-0.20230925092853-5b05b5c147d9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/sagernet/sing-box
- Affected
- < 1.4.5>= 1.5.0-beta.1, < 1.5.0-rc.5
- Fixed in
- 1.4.5, 1.5.0-rc.5
- Affected
- < 0.2.12-0.20230925092853-5b05b5c147d9
- Fixed in
- 0.2.12-0.20230925092853-5b05b5c147d9
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r5hm-mp3j-285g lists affected ranges: Go github.com/sagernet/sing-box >=0 =1.5.0-beta.1 =0 <0.2.12-0.20230925092853-5b05b5c147d9
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- EPSS
- CVE-2023-43644: 0.82% estimated exploitation activity in the next 30 days; percentile 57.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact This vulnerability allows specially crafted requests to bypass authentication, affecting all SOCKS inbounds with user authentication. Patches Update to sing-box 1.4.5 or 1.5.0-rc.5 and later versions. Workarounds Don't expose the SOCKS5 inbound to insecure environments.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-r5hm-mp3j-285g
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-43644 Advisory: sing-box vulnerable to improper authentication in the SOCKS inbound IDs: CVE-2023-43644, GHSA-r5hm-mp3j-285g Record: https://patchnext.com/advisories/cve-2023-43644 (revision 1, source checked 26 Oct 2026, 14:59 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/sagernet/sing-box 1.5.0-rc.5, 1.4.5; github.com/sagernet/sing 0.2.12-0.20230925092853-5b05b5c147d9. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/sagernet/sing-box: affected < 1.4.5; >= 1.5.0-beta.1, < 1.5.0-rc.5; fixed in 1.4.5, 1.5.0-rc.5 - Go github.com/sagernet/sing: affected < 0.2.12-0.20230925092853-5b05b5c147d9; fixed in 0.2.12-0.20230925092853-5b05b5c147d9 ## Suggested inspection (read-only) - Go github.com/sagernet/sing-box: check the installed version with your package manager. - Go github.com/sagernet/sing: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/sagernet/sing-box, github.com/sagernet/sing. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-r5hm-mp3j-285g (GitHub-reviewed advisory GHSA-r5hm-mp3j-285g lists affected ranges: Go github.com/sagernet/sing-box >=0 =1.5.0-beta.1 =0 <0.2.12-0.20230925092853-5b05b5c147d9) Commands are suggestions: review each one before running it.
Loading voting…