# sing-box vulnerable to improper authentication in the SOCKS inbound

Advisory record · `GHSA-r5hm-mp3j-285g`

- **Identifiers:** `GHSA-r5hm-mp3j-285g` · `CVE-2023-43644` · `GO-2023-2077`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 26 Sept 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 Sept 2023, 19:35 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/sagernet/sing-box` (Go): affected `<1.4.5 || >=1.5.0-beta.1, <1.5.0-rc.5`; fixed in `1.4.5`, `1.5.0-rc.5`
- `github.com/sagernet/sing` (Go): affected `<0.2.12-0.20230925092853-5b05b5c147d9`; fixed in `0.2.12-0.20230925092853-5b05b5c147d9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> sing-box versions before 1.4.5 and from 1.5.0-beta.1 before 1.5.0-rc.5 have an authentication bypass in their SOCKS inbounds that have user authentication enabled. A remote attacker can send specially crafted requests to get past authentication. Upgrade to sing-box 1.4.5 or 1.5.0-rc.5 or later. Until then, do not expose the SOCKS5 inbound to untrusted networks.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0082, the 58th percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:15 UTC: First seen by agentprime
- 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r5hm-mp3j-285g)

## Sources

- [GitHub Advisory Database: GHSA-r5hm-mp3j-285g](https://github.com/advisories/GHSA-r5hm-mp3j-285g)
- [OSV: GHSA-r5hm-mp3j-285g](https://osv.dev/vulnerability/GHSA-r5hm-mp3j-285g)
- <https://github.com/SagerNet/sing-box/security/advisories/GHSA-r5hm-mp3j-285g>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-43644>
- <https://github.com/SagerNet/sing-box/commit/9891fd672f5da9f20f59a1693271a946727f49e2>
- <https://github.com/SagerNet/sing/commit/5b05b5c147d9650e8accb4441e216c72a61f4859>
- <https://github.com/SagerNet/sing-box>
- <https://github.com/SagerNet/sing-box/releases/tag/v1.4.5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r5hm-mp3j-285g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r5hm-mp3j-285g/>. Everything for agents: <https://agentprime.io/llms.txt>.
