keycloak-services: keycloak-services: Token refresh continues issuing tokens for disabled audience clients

A flaw was found in the OIDC protocol implementation of Keycloak, an open-source identity and access management solution. The issue occurs during the token refresh process when the server restores requested audiences from stored client IDs. Keycloak fails to verify if the target audience client i...

Exploit for OS Command Injection in Asus Rt-Ax55_Firmware

CVE-2023-41346 — ASUS RT-AX55 — инъекция в token-refresh Лабо...

CVE-2026-111922

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

CVE-2026-111922

Vikunja versions 2.2.0 before 2.7.0 are vulnerable to a permissive CORS configuration that trusts all localhost and 127.0.0.1 ports with credentials, regardless of the service.publicurl setting. An attacker who controls a page on any localhost port can perform a credentialed request to the token ...

CVE-2026-111922 Vikunja 2.2.0 before 2.7.0 Permissive CORS Policy Trusting Localhost Origins

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

CVE-2026-111922 Vikunja 2.2.0 before 2.7.0 Permissive CORS Policy Trusting Localhost Origins

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

EUVD-2026-103290

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

CVE-2026-111922 Vikunja 2.2.0 before 2.7.0 Permissive CORS Policy Trusting Localhost Origins

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

CVE-2026-111922

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

CVE-2026-111922: Permissive Cross-domain Policy with Untrusted Domains

Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read t...

go-vikunja Vikunja configuration error vulnerability

The go-vikunja version from 2.2.0 to 2.7.0 had a configuration error vulnerability. This vulnerability stemmed from overly permissive CORS configurations. Even after setting service.publicurl, all localhost and 127.0.0.1 ports were trusted, and credentials were allowed to be carried. Attackers...

Vikunja: Permissive Cross-domain Security Policy trusts every localhost origin which should not be trusted

Summary Vikunja ships with cors.origins defaulting to http://127.0.0.1: and http://localhost:, and sends Access-Control-Allow-Credentials: true, so a page served from any port on the user's own machine may make credentialed cross-origin requests to the API and read the responses. The mandatory...

PT-2026-117123

Summary Vikunja ships with cors.origins defaulting to http://127.0.0.1: and http://localhost:, and sends Access-Control-Allow-Credentials: true, so a page served from any port on the user's own machine may make credentialed cross-origin requests to the API and read the responses. The mandatory...

PT-2026-116491

Name of the Vulnerable Software and Affected Versions Vikunja versions 2.2.0 through 2.6.9 Description The software has a permissive Cross-Origin Resource Sharing CORS configuration that trusts all ports on localhost and 127.0.0.1 with credentials, regardless of the service.publicurl setting. Thi...

CVE-2026-103869

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they...

EUVD-2026-94171

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they...

CVE-2026-103869

A flaw exists in pulp-ansible regarding the bearer-token refresh mechanism for collection remotes. The application incorrectly stores the access token in a module-level variable , causing it to be reused for every token download within a worker. An attacker capable of syncing an Ansible remote wi...

CVE-2026-103869

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they...

CVE-2026-103869 Pulp-ansible: bearer tokens are reused across remotes in a worker

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they...

CVE-2026-103869 Pulp-ansible: bearer tokens are reused across remotes in a worker

A flaw was found in pulp-ansible's bearer-token refresh for collection remotes. The access token is kept in one module-level variable and reused for every token download in that worker. A user who can sync an Ansible remote that uses token refresh, and can point that remote at a server they...