How do I check whether I am affected by CVE-2026-111691?

Check your deployed commit: git -C merge-base --is-ancestor ec86736beb1a3b9ca6ba0d1c48a1c415445b8dc4 HEAD. If it returns 0 and wimoor-common/common-mvc/.../UserInfoFilter.java still parses X-USERINFO unverified, you are affected. Exposure: from outside the gateway, test whether backend ports such as 8101 (erp) and the other service ports answer. Any answer means exposed.

What is the fix for CVE-2026-111691?

No patched version or commit published (no release tags; main unchanged). Mitigate: firewall or security-group every backend service port so only the gateway can reach them; expose only the gateway (8099). Have the gateway strip any inbound X-USERINFO. Longer term, sign the header (HMAC) or use mTLS and verify it in UserInfoFilter. Watch wimoor-erp/wimoor for a fix.

Who is not affected by CVE-2026-111691?

Not affected if: backend-ports-firewalled, gateway-only-access.

Live › vulnerability › CVE-2026-111691

Go to dashboard

critical9.1Other

WIMOOR through commit ec86736 contains an authentication bypass vulnerability that allows attackers to impersonate…

WIMOOR (wimoor-erp/wimoor, open-source Spring Cloud Amazon-seller ERP) trusts an unsigned X-USERINFO header in every backend service. Anyone who can reach a service port directly (erp 8101, gateway 8099) can forge companyid and usertype=manager/admin and read or write any tenant's data across 247 handlers. No fix exists yet. Found by static review only; not runtime-tested.

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

9.1

critical

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker reads and modifies other tenants' orders and finance data.
CVSS said: 9.1. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-111691

Go to dashboard

critical9.1Other

WIMOOR through commit ec86736 contains an authentication bypass vulnerability that allows attackers to impersonate…

Summary written from the sources below. Check the originals before acting.

CVSS 4.0

9.1

critical

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 16, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: network.
Worst case: Attacker reads and modifies other tenants' orders and finance data.
CVSS said: 9.1. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

WIMOOR through commit ec86736 contains an authentication bypass vulnerability that allows attackers to impersonate…

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

WIMOOR through commit ec86736 contains an authentication bypass vulnerability that allows attackers to impersonate…

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources