Search: auth.py
124 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Medium | 5.3 | EPSS 0.2% | CVE-2026-10175Aider · Code Injection Medium5.3EPSS 0.2%CVE Database V5CVE-2026-10175 A code injection vulnerability exists in Aider-AI Aider version 0.86.3 within the function editor_coder.run in the auth.py file of the Architect Mode component. This flaw allows remote attackers to inject code by manipulating the function. The vulnerability has a medium severity score of 5.3 and an exploit has been publicly released. The vendor has been informed but has not yet responded or provided a fix. | CVE Database V5 | ||
| Low | 3.7 | EPSS 0.4% | CVE-2026-48524jpadilla pyjwt · Improper Cleanup on Thrown Exception Low3.7EPSS 0.4%CVE Database V5CVE-2026-48524 > [!NOTE] > The vulnerability surfaces only when a JWKS fetch fails; an attacker can attempt to provoke that with sustained unknown-kid traffic, but the outcome depends on upstream JWKS-endpoint behavior (rate limiting, transient errors) which is beyond the attacker's control. Impact is reduced auth availability until the next successful fetch, not complete denial of service. ## Summary PyJWKClient.get_signing_key() forces a fresh HTTP request to the JWKS endpoint for every JWT with an unknown kid value, with no rate limiting. Since kid comes from the unverified token header, an attacker can trigger unlimited outbound requests. Additionally, fetch_data() finally block clears the JWKS cache on network error. ## Root Cause jwt/jwks_client.py:172-198 - get_signing_key(kid) calls get_signing_keys(refresh=True) for unknown kids, bypassing TTL cache with no cooldown. jwt/jwks_client.py:120-122 - finally block writes None to cache on error, clearing valid data. ## Impact - DoS against JWKS endpoint (unlimited requests per invalid token) - DoS against application (network I/O latency) - Cascading failure (rate limiting clears cache, breaking legitimate auth) ## Suggested Fix 1. Add refresh cooldown (refuse refresh more than once per TTL period) 2. Move cache write from finally to else block ## Affected Versions All versions with PyJWKClient (2.4.0 through 2.12.1) | CVE Database V5 | ||
| Medium | 5.5 | EPSS 0.1% | Medium5.5EPSS 0.1%GCVE DatabaseCVE-2026-46193 In the Linux kernel, the following vulnerability has been resolved: xfrm: ah: account for ESN high bits in async callbacks AH allocates its temporary auth/ICV layout differently when ESN is enabled: the async ahash setup appends a 4-byte seqhi slot before the ICV or auth_data area, but the async completion callbacks still reconstruct the temporary layout as if seqhi were absent. With an async AH implementation selected, that makes AH copy or compare the wrong bytes on both the IPv4 and IPv6 paths. In UML repro on IPv4 AH with ESN and forced async hmac(sha1), ping fails with 100% packet loss, and the callback logs show the pre-fix drift: ah4 output_done: esn=1 err=0 icv_off=20 expected_off=24 ah4 input_done: esn=1 auth_off=20 expected_auth_off=24 icv_off=32 expected_icv_off=36 Reconstruct the callback-side layout the same way the setup path built it by skipping the ESN seqhi slot before locating the saved auth_data or ICV. Per RFC 4302, the ESN high-order 32 bits participate in the AH ICV computation, so the async callbacks must account for the seqhi slot. Post-fix, the same IPv4 AH+ESN+forced-async-hmac(sha1) UML repro shows the corrected offset (ah4 output_done: esn=1 err=0 icv_off=24 expected_off=24) and ping succeeds; net/ipv4/ah4.o and net/ipv6/ah6.o build clean at W=1. IPv6 AH+ESN was not exercised at runtime, and the change has not been tested against a real async hardware AH engine. | GCVE Database | ||
| –Not rated | – | Reddit Cybersecurity A daily security digest reports 14 newly identified critical and high-severity supply-chain threats affecting npm, PyPI, and AI ecosystems as of 2026-05-26. Critical issues include credential harvesting and self-propagation malware in u/cap-js packages, a worm payload in u/beproduct/nestjs-auth, and a supply chain compromise in guardrails-ai. High-severity vulnerabilities include denial-of-service (DoS) attacks in Parse Server and other npm packages, remote code execution (RCE) in AI toolchains Diffusers and lmdeploy, SSRF vulnerabilities in Crawlee and SillyTavern, and injection or hijacking attacks in samlify and js-cookie. Immediate remediation actions are recommended for critical packages, including upgrading or uninstalling affected versions. Several vulnerabilities enable denial-of-service or remote code execution, posing significant risk if exploited. | Reddit Cybersecurity | |||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d747cc7acd8bbc1defbf475aa3202fd332fd43135a6fedddfcc37356ce02eb54) Package presents itself as the legitimate slopus/happy CLI (README instructs `npm install -g happy`; homepage, repository, bugs, and author fields all point at happy.engineering / github.com/slopus/happy), but the published name is ggk-happy and the shipped code has been modified in ways that harm installers: 1. Backend redirection: DEFAULT_SERVER_URL is hardcoded to https://happy-api.ask-ggk.com and DEFAULT_WEBAPP_URL to https://happy.ask-ggk.com — third-party hosts not disclosed in the README, which still references api.cluster-fluster.com. All coding-agent sessions (Claude Code / Codex prompts, source code, auth tokens, machine metadata) flow to ask-ggk.com instead of the publisher advertised in package metadata. 2. Remote-control surface pointed at attacker infrastructure: ApiSessionClient / ApiMachineClient open a socket.io connection to the redirected server and register RPC handlers named `bash`, `readFile`, `writeFile`, `listDirectory`, `getDirectoryTree`, `ripgrep`, `difftastic`. The `bash` handler runs `execAsync(data.command, options)` on parameters supplied by the remote server. Whoever operates happy-api.ask-ggk.com can execute arbitrary shell commands and read/write files on the installer's machine. 3. Install-time auto-takeover: scripts/postinstall.cjs, on global or root install, unconditionally spawns `node bin/happy.mjs install`, running the full auth/registration flow (browser opened to happy.ask-ggk.com, machine registered to happy-api.ask-ggk.com, daemon started) at `npm install -g` time. Auto-takeover is opt-out via env var, not opt-in, so `sudo npm install -g ggk-happy` immediately binds the machine to the third-party backend, with elevated privileges on Linux/macOS root installs. 4. Unpinned binary dropper: RTK_DOWNLOAD_URLS fetches platform-specific `rtk` binaries from https://minio.ask-ggk.com/happy/rtk-*.{zip,tar.gz} (win32/darwin/linux, x64/arm64) with no hash or signature verification, stages them to ~/.local/share/ggkhappy/rtk/bin/rtk (or %LOCALAPPDATA%\ggkhappy\rtk\bin\rtk.exe), and later invokes them via execFile. Purpose of the binary is not documented. 5. Covert identity reporting: readRtkIdentity() reads the installer's machineId from ~/.happy settings and the auth token from ~/.happy/access.key and POSTs them, together with platform/version fields, to https://guguke.ask-ggk.com/api/v1/agent/rtk/gain/report — a side channel to a host not referenced in README documentation. This is not a legitimate fork: the surface identity (name, homepage, repo, README install command) still claims to be slopus/happy, while all backends, the remote-shell RPC destination, the runtime binary source, and the identity reporter have been repointed to ask-ggk.com infrastructure. Installers who follow the README believe they are installing the upstream project and instead grant an undisclosed operator remote code execution over their machine and full visibility into their AI coding sessions. | GCVE Database | |||
| High | 8.1 | EPSS 0.2% | CVE-2026-44304Netflix lemur · LDAP Injection High8.1EPSS 0.2%CVE Database V5CVE-2026-44304 Lemur manages TLS certificate creation. Prior to 1.9.0, Lemur's LDAP authentication module (lemur/auth/ldap.py) constructs LDAP search filters using unsanitized user input via Python string interpolation. An authenticated LDAP user can inject LDAP filter metacharacters through the username field to manipulate group membership queries and escalate their privileges to administrator. This vulnerability is fixed in 1.9.0. | CVE Database V5 | ||
| High | 8.1 | EPSS 0.6% | CVE-2026-42859any1 neatvnc · Classic Buffer Overflow High8.1EPSS 0.6%CVE Database V5CVE-2026-42859 Neat VNC is a VNC server library. Prior to 0.9.6, a pre-authentication stack buffer overflow exists in neatvnc in the RSA-AES security type handler. An unauthenticated remote attacker who can reach the VNC listening socket can send a crafted security type 5 (RSA-AES) or security type 129 (RSA-AES-256) handshake with an oversized client RSA public key, causing rsa_aes_send_challenge in src/auth/rsa-aes.c to overflow a 1024-byte on-stack buffer when encrypting the server challenge. This results in at least a denial of service via server crash. This vulnerability is fixed in 0.9.6. | CVE Database V5 | ||
| Critical | 9.0 | EPSS 0.4% | CVE-2026-41588inducer relate · Timing Side Channel Critical9.0EPSS 0.4%CVE Database V5CVE-2026-41588 RELATE is a web-based courseware package. Prior to commit 2f68e16, there is a timing attack vulnerability in course/auth.py — check_sign_in_key(). This issue has been patched via commit 2f68e16. | CVE Database V5 | ||
| High | 8.4 | EPSS 0.2% | CVE-2026-44334MervinPraison PraisonAI · Code Injection High8.4EPSS 0.2%CVE Database V5CVE-2026-44334 PraisonAI is a multi-agent teams system. From version 4.5.139 to before version 4.6.32, CVE-2026-40287's fix gated tools.py auto-import behind PRAISONAI_ALLOW_LOCAL_TOOLS=true in two files (tool_resolver.py, api/call.py). A third import sink in praisonai/templates/tool_override.py was missed and remains unguarded. It is reached by the recipe runner on every recipe execution and is remotely triggerable through POST /v1/recipes/run with a recipe value pointing at any local absolute path or any GitHub repo (because SecurityConfig.allow_any_github defaults to True). The attacker drops a tools.py next to TEMPLATE.yaml; the server exec_module()s it. No auth required by default, no environment opt-in required. This issue has been patched in version 4.6.32. | CVE Database V5 | ||
| High | 8.7 | EPSS 0.3% | CVE-2026-41505inducer relate · PRNG High8.7EPSS 0.3%CVE Database V5CVE-2026-41505 RELATE is a web-based courseware package. Prior to commit 2f68e16, RELATE is vulnerable to predictable token generation in auth.py's make_sign_in_key() function and exam.py's gen_ticket_code() function. This issue has been patched via commit 2f68e16. | CVE Database V5 | ||
| Medium | 5.3 | EPSS 0.3% | Medium5.3EPSS 0.3%CVE Database V5CVE-2026-7713 A vulnerability was detected in crocodilestick Calibre-Web-Automated up to 4.0.6. Affected by this vulnerability is the function generate_auth_token of the file cps/kobo_auth.py of the component Kobo auth-token Route. The manipulation results in improper authorization. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.0.7 addresses this issue. The patch is identified as 9f50bb2c16160564c9f8777dc2ceed3eb95e4807. The affected component should be upgraded. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| Medium | 6.9 | EPSS 0.3% | CVE-2026-7579AstrBotDevs AstrBot · Hard-coded Credentials Medium6.9EPSS 0.3%CVE Database V5CVE-2026-7579 A security vulnerability has been detected in AstrBotDevs AstrBot up to 4.16.0. This issue affects some unknown processing of the file astrbot/dashboard/routes/auth.py of the component Dashboard. The manipulation leads to hard-coded credentials. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way. EPSS 0.3%Vulnerability | CVE Database V5 | ||
| Critical | 9.1 | EPSS 0.8% | CVE-2025-22871Red Hat Security Advisory: OpenShift Container Platform 4.12.87 bug fix and security update Critical9.1EPSS 0.8%GCVE DatabaseCVE-2025-22871 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-eda-controller: Template Injection via Git Branch and Refspec in EDA Projects (CVE-2025-49521) * automation-eda-controller: Authenticated Argument Injection in Git URL in EDA Project Creation (CVE-2025-49520) * automation-gateway-proxy: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * automation-gateway-proxy-openssl30: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * automation-gateway-proxy-openssl32: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) * receptor: Request smuggling due to acceptance of invalid chunked data in net/http (CVE-2025-22871) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation Platform * Updated API error messaging to be more helpful in the event a user logs in as the admin user via legacy auth on one component, then tries to do so via the other component (AAP-47541) * Fixed an issue where API records could be missing or duplicated across pages (AAP-47504) * Refactored V1RootView.get() and improve reverse lookup logic (AAP-47366) * Refactored process_statuses() method to reduce its cognitive complexity (AAP-47341) * Improved accuracy of openapi API docs and schema (AAP-46639) * Reduced the cognitive complexity of method migrate_resource() in migrate_service_data.py from 56 to <=15 (AAP-45822) * Reduced the cognitive complexity of the process_fields() method in serializers/preference.py file (AAP-45820) * Reduced the cognitive complexity of unique_fields_for_model() method to below 15 (AAP-45819) * Enable query filtering for fields user_ansible_id, team_ansible_id, and object_ansible_id on the role assignment API endpoints (AAP-45443) * The Survey form is displayed for a Worlflow visualizer Job template or Workflow Job template node with a survey enabled and no Prompt on Launch fields (AAP-47732) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-47668) * The API feature flags used to hide references to Policy as Code in the UI have been removed. All Policy as Code fields appear for all users at all times (AAP-47006) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-46813) * On the inventory source form, for a source type of 'VMware ESXi' the user will be able to select credentials of type 'VMware vCenter' (AAP-46784) * Fixed a bug when selecting the 'Comparison' field for Atrriibute trigger in the Authenticator Map form (AAP-46555) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-45834) * added an extra validation to handle incorrect user input in the variables field, as the API doesn't return an error for it (AAP-42563) * Fixed a bug that was causing the UI to throw an error when launching a workflow job template with both "Prompt on Launch" and "Survey" enabled (AAP-42303) * The Hosts links in the Resource Counts section of the overview page were fixed to redirect to the Hosts page (AAP-42288) * Allows role assignments using object_ansible_id in the role_user_assignment module (AAP-48042) * Improved documentation and examples related to object_id and object_ansible_id parameters in role_user_assignment module (AAP-48041) * Allows object_id field in role_user_assignment module to accept a list of items (AAP-47979) * Fixed an example task in ansible.platform.token module (AAP-47976) * Specify correct aap_* parameters in ansible.platform.token module (AAP-47975) * Improved documentation and examples for authenticator and authenticator_map modules (AAP-45982) * Updated documentation examples for the ansible.platform.settings module with tested tasks examples (AAP-45954) * Added a new section in the collection README describing how to authenticate to AAP from the playbook (AAP-45578) * Ensures that modules in the ansible.platform collection accepts AAP_* variable for authentication (AAP-45363) * Fixed ansible.platform.user not adding users to organizations (AAP-45248) * Allows running ansible.platform collection modules in check_mode (AAP-45246) * Ad | GCVE Database | ||
| Critical | 9.1 | EPSS 4.4% | CVE-2026-0545mlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization Critical9.1EPSS 4.4%GCVE DatabaseCVE-2026-0545 Mlflow versions up to 3.10.1 have a critical vulnerability where FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization when basic-auth is enabled. This allows any network client to submit, read, search, and cancel jobs without credentials if job execution is enabled and jobs are allowlisted. The flaw can lead to unauthenticated remote code execution if allowed jobs perform privileged actions. Even if jobs are safe, this bypass constitutes an authentication bypass that can cause job spam, denial of service, or data exposure. | GCVE Database | ||
| High | 8.2 | EPSS 0.2% | CVE-2026-27124jlowin fastmcp · Confused Deputy High8.2EPSS 0.2%CVE Database V5CVE-2026-27124 ## Summary While testing the *GitHubProvider* OAuth integration, which allows authentication to a FastMCP MCP server via a FastMCP OAuthProxy using GitHub OAuth, it was discovered that the FastMCP OAuthProxy does not properly validate the user's consent upon receiving the authorization code from GitHub. In combination with GitHub’s behavior of skipping the consent page for previously authorized clients, this introduces a Confused Deputy vulnerability. ## Technical Details An adversary can initiate an authentication flow by connecting their malicious MCP client to a benign MCP server using the *GitHubProvider* OAuth integration. During this flow, the attacker consents to connect their client to the MCP server and, at that point, can capture the GitHub authorization URL they are redirected to after granting consent. The attacker can then lure a victim, who is already logged into GitHub and has previously connected an MCP client to the benign MCP server, to open this captured URL. As a result, the victim’s browser is immediately redirected to the OAuthProxy’s callback endpoint, which does not correctly enforce that this browser has just given consent. The OAuthProxy then redirects the victim’s browser to the malicious MCP client’s callback URL with a valid authorization code. The attacker can exchange this code for an access token to the benign MCP server associated with the victim’s GitHub account, potentially gaining unauthorized access to resources tied to that account. Although this issue was verified in practice only for the *GitHubProvider*, a review of the source code, specifically the `OAuthProxy._handle_idp_callback` [function](https://github.com/jlowin/fastmcp/blob/ee5f465a82350e1c5a56c4a2b47cfdc4cd736e76/src/fastmcp/server/auth/oauth_proxy.py#L1762), shows that the IdP callback handler does not verify whether the browser sending the `state` and `code` has previously consented to connecting the client to the server. As long as a valid `state` and `code` pair is provided, the OAuthProxy requests an access token from the IdP and then redirects the user-agent to the client’s callback URL with a new `code` and the corresponding `state`, allowing the client to retrieve the access token from the proxy. This pattern causes all OAuth integrations whose IdP allows skipping the consent page to be vulnerable to this attack. Skipping the consent page is not, by itself, a vulnerability on the IdP side. Many providers legitimately skip consent for first-party or previously authorized clients with the same scopes. In this case, the core problem lies in the OAuthProxy callback handler not correctly verifying that the browser issuing the callback request is the same one that has just given the required consent. ## Steps to reproduce 1. Set up an MCP server using the *GitHubProvider* integration. 2. Connect a benign MCP client to this MCP server. 3. Configure your default browser to route all traffic through an interception proxy such as Burp Suite. 4. In a private browsing window or a second browser, log into the GitHub account used in step 2. 5. As the attacker, connect a new (malicious) MCP client to the MCP server from step 1. 6. When the browser opens for the attacker’s client, enable interception in your proxy. 7. In the browser, confirm the consent prompt. 8. In the proxy, forward all requests up to the authorization request to the GitHub authorization server. 9. Copy the authorization URL and drop the intercepted request. 10. Simulate luring the victim onto the URL by opening this URL in the browser window opened in step 4. 11. Observe that the malicious client receives a valid authorization code and gains access to the benign MCP server using the victim’s GitHub account. In a more realistic scenario, the malicious client could be a public MCP client or a simple web server that logs the received authorization code or token, which the attacker then uses to obtain the access token and connect to the MCP server as the victim. ## Recommendation To mitigate this issue, the OAuthProxy should verify that the browser sending the authorization code has actually given consent for the corresponding client. This can be achieved by setting and validating a consent cookie or similar browser-bound state, as described in the [mitigations section](https://mcp.mintlify.app/specification/2025-11-25/basic/security_best_practices#mitigation) for this vulnerability in the MCP specification. | CVE Database V5 | ||
| High | 7.5 | EPSS 1.1% | CVE-2025-14550Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update High7.5EPSS 1.1%GCVE DatabaseCVE-2025-14550 Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: wheel: Privilege Escalation or Arbitrary Code Execution via malicious wheel file unpacking (CVE-2026-24049) * automation-controller: pyasn1 has a DoS vulnerability in decoder (CVE-2026-23490) * automation-gateway: React Router vulnerable to XSS via Open Redirects (CVE-2026-22029) * python3.11-aiohttp: AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb (CVE-2025-69223) * python3.11-django: Django: SQL injection via crafted column aliases in QuerySet.order_by() (CVE-2026-1312) * python3.11-django: Django: SQL Injection via crafted column aliases (CVE-2026-1287) * python3.11-django: Django: Denial of Service via crafted HTML inputs (CVE-2026-1285) * python3.11-django: Django: SQL Injection via RasterField band index parameter (CVE-2026-1207) * python3.11-django: Django: Denial of Service via crafted request with duplicate headers (CVE-2025-14550) * python3.11-protobuf: Denial of Service in Python Protobuf (CVE-2026-0994) * receptor: Memory exhaustion in query parameter parsing in net/url (CVE-2025-61726) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: * Python has been updated to 3.12 (AAP-56567) IMPORTANT: All users must download the latest version of the installer. Attempting to install or upgrade with a previous version of the installer could result in failure. Automation Platform * The OpenAPI gateway spec is now accurate for the legacy_auth endpoint (AAP-63422) * Fixed a bug that was preventing users from viewing complete survey question choices that contained a colon (AAP-66389) * Added source control branch option for inventory source form (AAP-63544) * automation-gateway has been updated to 2.5.20260225 Automation controller * Added token auth to 2.5 (AAP-65488) * Fixed the job list endpoint to no longer load the job artifacts, resulting in better performance (AAP-63221) * Enabled cross-organization credential sharing for teams. The changes were made in the legacy RBAC functionality (AAP-54804) * automation-controller has been updated to 4.6.26 Automation hub * Updated _ui/v2 endoints to properly enforce RBAC permissions (AAP-66638) * Added a static OpenAPI spec to galaxy that focuses the potential endpoints users can call (AAP-66417) * automation-hub has been updated to 4.10.12 Event-Driven Ansible * Overrode RQ's default heartbeat to call register_birth, allowing worker re-registration in case of worker disconnects from Redis, and also eliminating Ghost Workers. Also, bump rq version to 2.6.1, which is a more recent and stable release (AAP-56872) * automation-eda-controller has been updated to 1.1.16 Container-based Ansible Automation Platform * containerized installer setup has been updated to 2.5-22 RPM-based Ansible Automation Platform * Fixed an issue where restore was not properly generating SSL certificate for redis in cluster mode (AAP-60991) * ansible-automation-platform-installer and installer setup have been updated to 2.5-21 Additional changes: * ansible-core has been updated to 2.16.16 * All python3.11- prefixed rpms are replaced with python3.12- prefixed rpms | GCVE Database | ||
| Medium | 6.1 | EPSS 0.3% | Medium6.1EPSS 0.3%CVE Database V5CVE-2026-28350 ### Summary The `<base>` tag passes through the default `Cleaner` configuration. While `page_structure=True` removes `html`, `head`, and `title` tags, there is no specific handling for `<base>`, allowing an attacker to inject it and hijack relative links on the page. ### Details The `<base>` tag is not currently in the `page_structure` kill set. Even though the specification says `<base>` must be inside `<head>`, browsers accept `<base>` tags outside of the head. If an attacker injects a `<base>` tag, it changes the base URL for all relative URLs on the page (links, images, scripts) to a domain controlled by the attacker. ### PoC ```python from lxml_html_clean import clean_html # The base tag is preserved in the output result = clean_html('<base href="http://evil.com/"><a href="/account">Account</a>') print(result) # Output: <div><base href="http://evil.com/">...<a href="/account">Account</a></div> ``` ### Impact The injection of a `<base>` tag allows an attacker to hijack the resolution of **all** relative URLs on the page. This results in three critical attack vectors: 1. **Phishing & Redirection:** Attackers can redirect user navigation (e.g., `<a href="/login">`) and form submissions (e.g., `<form action="/auth">`) to an attacker-controlled domain, effectively stealing credentials or sensitive data without the user realizing they have left the legitimate site. 2. **Cross-Site Scripting (XSS):** If the victim application loads JavaScript files using relative paths (e.g., `<script src="assets/app.js">`), the browser will attempt to fetch the script from the attacker's domain. This upgrades the vulnerability from HTML injection to full Stored XSS. 3. **Defacement:** Relative references to images (`<img>`) and stylesheets (`<link>`) will be loaded from the attacker's server, allowing for UI redressing or defacement. | CVE Database V5 | ||
| Medium | 6.3 | EPSS 0.2% | Medium6.3EPSS 0.2%CVE Database V5CVE-2025-15598 A vulnerability was found in Dataease SQLBot up to 1.5.1. This impacts the function validateEmbedded of the file backend/apps/system/middleware/auth.py of the component JWT Token Handler. Performing a manipulation results in improper verification of cryptographic signature. The attack can be initiated remotely. The attack is considered to have high complexity. The exploitability is said to be difficult. The exploit has been made public and could be used. A comment in the source code warns users about using this feature. The vendor was contacted early about this disclosure. EPSS 0.2%Vulnerability | CVE Database V5 | ||
| High | 7.8 | EPSS 0.1% | High7.8EPSS 0.1%CVE Database V5CVE-2025-4960 The com.epson.InstallNavi.helper tool, deployed with the EPSON printer driver installer, contains a local privilege escalation vulnerability due to multiple flaws in its implementation. It fails to properly authenticate clients over the XPC protocol and does not correctly enforce macOS’s authorization model, exposing privileged functionality to untrusted users. Although it invokes the AuthorizationCopyRights API, it does so using overly permissive custom rights that it registers in the system’s authorization database (/var/db/auth.db). These rights can be requested and granted by the authorization daemon to any local user, regardless of privilege level. As a result, an attacker can exploit the vulnerable service to perform privileged operations such as executing arbitrary commands or installing system components without requiring administrative credentials. | CVE Database V5 |
Page 6 of 7 · 1 duplicate CVE record merged