Skip to main content

Sencho CVE-2026-108522

| EUVDEUVD-2026-96729 MEDIUM
Improper Authentication (CWE-287)
2026-10-11 cna@vuldb.com GHSA-5mq8-98f7-6q76
5.5
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach /api/auth/login remotely
  2. Delivery
    Submit login with spoofed X-Forwarded-For
  3. Exploit
    Rotate forwarded IP each request
  4. Execution
    Evade per-IP rate limiter
  5. Persist
    Brute-force valid credentials
  6. Impact
    Authenticate to targeted account

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a Sencho instance (≤0.94.1) deployed WITHOUT a correctly configured trusted-proxy boundary - in vulnerable versions the login limiter honored client-supplied X-Forwarded-For unconditionally, so default/typical deployments are affected. The attacker only needs remote network reach to /api/auth/login and no authentication (CVSS PR:N). LIMITING FACTORS: the flaw itself only defeats the per-IP failed-attempt rate limiter; it does not directly grant access, so the attacker must still brute-force or guess valid credentials to actually authenticate. The fix mitigates by ignoring forwarding headers unless they originate from explicitly configured proxy CIDRs (SENCHO_TRUSTED_PROXY_CIDRS) and by adding a failed-attempt limit keyed to normalized account identity, so instances already fronted by a correctly trusted proxy and patched are not exposed.

Impact

This is a medium-severity authentication-control weakness, not a direct auth bypass. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes remote, low-complexity, unauthenticated reachability with uniformly LOW impact across all metrics (VC:L/VI:L/VA:L and subsequent SC:L/SI:L/SA:L), and E:P marks exploit maturity as Proof-of-Concept - consistent with the report that exploit code has been made public. No CISA KEV listing and no EPSS score were provided in the input, so there is no signal of widespread or automated real-world exploitation; absence of EPSS means probability of exploitation cannot be quantified here. The vendor statement clarifies the true nature: the login limiter trusted client-supplied X-Forwarded-For with no trusted-proxy boundary, so an attacker can rotate the apparent client address to defeat per-IP rate limiting - this facilitates credential brute-force/stuffing rather than granting authentication by itself. Net assessment: a legitimate but moderate issue (not a critical, directly-exploitable auth bypass). The CWE-287 'improper authentication' label and the 'Authentication Bypass' tag slightly overstate impact relative to the vendor's description of a rate-limiter evasion; defenders should read this as a brute-force protection bypass. Priority is elevated by public PoC availability but tempered by low impact scoring and the dependency on separately brute-forcing valid credentials.

Exploit ScenarioDerived

A remote, unauthenticated attacker targets the /api/auth/login endpoint of an internet-reachable Sencho instance (≤0.94.1) that trusts forwarding headers by default. By rotating the X-Forwarded-For value on each request, the attacker makes every login attempt appear to originate from a different client IP, defeating the per-IP failed-attempt limiter and enabling unthrottled password brute-force or credential-stuffing against user accounts. Public proof-of-concept exploit code exists (published as a GitHub gist), lowering the barrier to reproduction.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 11, 2026

Improper authentication in Studio-Saelix Sencho (through 0.94.1) lets remote unauthenticated attackers manipulate the X-Forwarded-For header on the /api/auth/login endpoint to rotate their apparent client address and defeat the per-IP failed-login rate limiter. Exploitation requires network reach to the login endpoint on an instance deployed without a correctly configured trusted-proxy boundary, which matches default/typical deployments; publicly available exploit code exists, though CISA KEV does not list this CVE and no confirmed in-the-wild exploitation has been reported. The weakness is a control bypass rather than a direct login bypass - the attacker must still brute-force or guess valid credentials - so its practical impact is medium severity (CVSS 4.0 base 5.5; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), primarily enabling credential-stuffing and password-guessing at scale.

RemediationAI

Apply the upstream fix - commit 79b86ddcd4aefdd6941f098e35990ab397b13c72, delivered via pull request https://github.com/Studio-Saelix/sencho/pull/1877 - and upgrade Sencho beyond 0.94.1; upstream fix available (PR/commit); released patched version not independently confirmed, so confirm the tag containing this commit before relying on a packaged release. After upgrading, set SENCHO_TRUSTED_PROXY_CIDRS to the narrowest possible value for your topology (a single IPv4 proxy as /32, a single IPv6 proxy as /128, or the exact proxy network CIDR); leaving it unset or invalid makes Sencho ignore forwarded client and scheme data, which is the safe default but will treat non-TLS Pilot Agent upgrades as non-confidential and skip hub registry credential delivery, so explicitly configuring the proxy CIDR is required if you rely on TLS termination signaling. Do not set the CIDR to a permissive range such as 0.0.0.0/0 - that reintroduces the spoofing condition the patch removes. Until patching is possible, the practical compensating controls are: block direct external access to /api/auth/login so the endpoint is reachable only through the reverse proxy (trade-off: requires network/firewall changes and breaks any direct-to-app clients); strip and re-set X-Forwarded-For at the edge so client-supplied values never reach the application (trade-off: misconfiguration can corrupt legitimate client-IP logging); enforce independent login throttling and lockout at the reverse proxy using its own trusted client-IP logic (for example nginx limit_req with set_real_ip_from, or equivalent WAF/API-gateway controls) rather than the application limiter; and add account-identity-based failed-attempt limits plus MFA or a strong credential policy, since the flaw only defeats the per-IP limiter and the attacker must still guess valid credentials. Trade-off for the edge-only approach: it does not protect instances whose application port remains directly reachable. Additional references: https://vuldb.com/vuln/416188 and https://vuldb.com/cve/CVE-2026-108522.

Affected VersionsENISA

Sencho 0.94.1
Sencho 0.94.0

Affected Packages

euvd sencho no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Sencho is a self-hosted platform whose backend exposes /api/auth/login; the login rate limiter identified clients by the address derived from the X-Forwarded-For header without validating that the request came from a trusted reverse proxy (CWE-287, improper authentication). Because the header is client-supplied, any remote unauthenticated client could send a different value per request, giving each attempt a fresh identity for rate-limiting purposes and effectively removing the per-IP throttle. The upstream fix (commit 79b86ddcd4aefdd6941f098e35990ab397b13c72, PR #1877) inverts the trust model: forwarding headers are ignored by default, honored only when the immediate peer falls inside explicitly configured proxy CIDRs (SENCHO_TRUSTED_PROXY_CIDRS, given as /32 for a single IPv4 proxy or /128 for IPv6), and a separate failed-attempt counter keyed by normalized account identity is added so throttling no longer depends solely on a spoofable address. The same commit generalizes trusted-proxy handling beyond the earlier X-Forwarded-Proto/Pilot Agent TLS-termination use case, introduces a trustedLoopback option and an undici dependency, and adds tests confirming that a forwarded HTTPS scheme from an untrusted peer is ignored on /api/diagnostics/environment. Affected deployments are those where the application is reachable without a correctly trusted proxy in front of it; instances already fronted by a properly configured trusted proxy and running the patched code are not exposed.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P
vuln.today AI 6.5 MEDIUM

Remote unauthenticated header manipulation (AV:N/AC:L/PR:N/UI:N) defeats login rate limiting, enabling credential brute-force with low resulting confidentiality/integrity impact and no availability effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vuldb).

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
Low
Subsequent system: Integrity
Low
Subsequent system: Availability
Low

DescriptionCVE.org

A vulnerability was found in Studio-Saelix Sencho up to 0.94.1. This affects an unknown part of the file /api/auth/login of the component Login Endpoint. Performing a manipulation of the argument X-Forwarded-For results in improper authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The patch is named 79b86ddcd4aefdd6941f098e35990ab397b13c72. To fix this issue, it is recommended to deploy a patch. The vendor confirms: "The login limiter relied on client-supplied X-Forwarded-For data without an explicit trusted-proxy boundary, allowing an attacker to rotate the apparent client address. The remediation now ignores forwarding headers by default, accepts them only from explicitly configured proxy CIDRs, and adds a separate failed-attempt limit keyed by normalized account identity."

Threat Intelligence Overview

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Rare
obscure open-source project by a small studio, negligible production footprint
Social Media
2
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy