Description
OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.11, OPNsense\Core\ACL::hasPrivilege() appends a directly assigned comma-separated <priv> value as one string and then uses an exact comparison when checking user-config-readonly. A user directly assigned both a component write privilege and user-config-readonly can therefore be treated as lacking the read-only restriction, and MVC APIs protected by throwReadOnly() can persist configuration changes for that component. Group privileges are not affected by the same parser flaw because the group path already splits comma-separated values. This issue is fixed in version 26.1.11.
References5
- github.com/opnsense/core/commit/578e025111161ffd03fd3fd0ccdac20…
- github.com/opnsense/core/commit/e15a884973746319e79bd2cd421e8a0…
- github.com/opnsense/core/commit/f674f4ff294a3f7c4cd0591563f6df4…
- github.com/opnsense/core/security/advisories/GHSA-p9pr-782r-w2xw
- github.com/opnsense/core/security/advisories/GHSA-p9pr-782r-w2xw
Metrics
- CVSS 3.1
-
7.1
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L - EPSS — exploit probability
- 0% percentile: 32 · as of 10 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.