CVE-2026-84728 · Package
NO FIX YET · SEE WHAT TO DO
In Apache OFBiz 24.09 before 24.09.08 with multitenancy enabled, a logged-in user of one tenant can send their own tenant ID at login to act against another tenant's hostname. The permission check runs against the attacker's tenant while reads and writes hit the other tenant's data.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only deployments of Apache OFBiz 24.09 before 24.09.08 with documented multitenancy enabled are exposed. The attacker needs a valid low-privilege account in one tenant, and the flaw works against a hostname mapped to another tenant. Single-tenant installs are not described as affected.
Not affected if multitenancy-disabled, single-tenant, version-24.09.08-or-later
Who cares apache-ofbiz, erp, multitenancy
24.09.x in the deployed build or release notes.24.09.08.Incorrect Authorization in Apache OFBiz 24.09 before 24.09.08 on all platforms, when documented multitenancy is enabled, allows a remote authenticated attacker holding only a valid low-privilege account in one tenant to read and write data belonging to a different tenant, by submitting their own tenant's userTenantId alongside their own credentials to the normal Party Manager login against a hostname mapped to a different tenant: ContextFilter resolves the tenant from the hostname via TenantDomainName, but LoginWorker gives priority to the conflicting userTenantId request parameter and authenticates against the attacker's own tenant, so a subsequent ordinary request to the same hostname combines the hostname-mapped tenant's Entity Engine delegator with the attacker's tenant's session dispatcher, security object, and identity, letting the permission check run against the attacker's own tenant while the resulting read or write is performed against the hostname-mapped tenant's data. Users are recommended to upgrade to version 24.09.08, which fixes this issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.