CVE-2026-134169
Qwik City before 1.20.3 (@builder.io/qwik-city) and @qwik.dev/router before 2.0.0-rc.4 contain an improperly controlled object modification
CVSS
7.5
High
EPSS
—
KEV
—
Exploit Today
—
0-100
Published: Nov 20, 2026 · Last modified: Nov 20, 2026 · CWE-915
Not enough EPSS history yet.
Qwik City before 1.20.3 (@builder.io/qwik-city) and @qwik.dev/router before 2.0.0-rc.4 contain an improperly controlled object modification vulnerability in formToObj that allows unauthenticated attackers to overwrite built-in function properties. Attackers can send a form POST with nested field names traversing inherited members of string values, breaking Object.prototype.hasOwnProperty.call process-wide until server restart.
- github.comhttps://github.com/QwikDev/qwik/blob/12eb9716611fade0f3c99809be5e9dd1196fce7f/packages/qwik-city/src/middleware/request-handler/request-event.ts#L510-L513
- github.comhttps://github.com/QwikDev/qwik/commit/5e95c55e03c23efbf604118b8abe3a52554096ca
- github.comhttps://github.com/QwikDev/qwik/commit/f643573c49bb39a1bad08f63e848b053bf2de569
- github.comhttps://github.com/QwikDev/qwik/releases/tag/%40builder.io%2Fqwik-city%401.20.3
- github.comhttps://github.com/QwikDev/qwik/releases/tag/%40qwik.dev%2Frouter%402.0.0-rc.4
- github.comhttps://github.com/QwikDev/qwik/security/advisories/GHSA-cvf2-p22x-xw37
- www.vulncheck.comhttps://www.vulncheck.com/advisories/qwik-city-before-1.20.3-and-router-before-2.0.0-rc.4-dos-via-formtoobj
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-540398.1 HIG—
———LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.7.0 until 0.8.6, when local registration is enabled and at least one social provider is configured, POST /api/auth/register passes an unparsed request object into api/server/services/AuthService.js, allowing an unauthenticated attacker to persist a forged provider value for a known victim email. The api/strategies/socialLogin.js email-fallback path then accepts the planted record when the victim signs in because it compares the stored provider name without requiring the provider subject identifier. The victim OAuth session and the attacker local-password session become bound to the same user record, giving the attacker persistent read and write access to data created by the victim. The first-user administrator role is an additional conditional impact only on a fresh deployment. This issue is fixed in version 0.8.6.7hCVE-2026-1041847.1 HIG—
———LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, LinkController::update() in app/Http/Controllers/API/LinkController.php passes $request->all() to the repository update method even though user_id is fillable and is not an allowed field in the validated update request. An authenticated API user who is authorized to update a link can therefore assign an arbitrary or nonexistent user_id, transferring the link into another user's bookmark collection or orphaning it from any real account. The web update controller is unaffected because it passes only validated fields. This issue is fixed in version 2.6.0.10hCVE-2026-1312844.3 MED—
——0In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause Representational State Transfer (REST) API clients and filters to use incorrect artifact state.
The vulnerability is possible because container archive import accepts artifact workflow state from the archive instead of deriving that state from associated cases and notes.
For more information see Splunk SOAR REST API reference (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference) in the Splunk documentation.1dCVE-2026-1312755.4 MED—
——0In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analysts and cause configured data retention strategies to delete affected records earlier than intended.
The vulnerability is possible because the REST API accepts client-supplied values for timestamps that Splunk SOAR uses to order records and apply data retention.
The early deletion impact requires an applicable data retention strategy; the timeline impact does not.
For more information see Manage your PostgreSQL database with data retention strategies (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.0/manage-your-splunk-soar-on-premises-system-health-and-performance/manage-your-postgresql-database-with-data-retention-strategies) in the Splunk documentation.15hCVE-2026-1312575.4 MED—
——0In Splunk SOAR versions below 8.8.0, a user with permission to view and edit containers and at least one container label could set misleading user and app provenance on containers that the user creates and learn whether user IDs and installed app identifiers exist.
The vulnerability is possible because the Representational State Transfer (REST) API accepts client-supplied values for server-managed container fields.8hCVE-2026-1312505.4 MED—
——0In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.15h