User enumeration via a timing side channel in ApostropheCMS versions 4.28.0 and prior allows unauthenticated attackers to identify valid usernames and emails. The password reset endpoint fails to normalize response time when a valid user is found, enabling an attacker to distinguish valid accounts from invalid ones by repeatedly probing the endpoint. This can facilitate credential stuffing and targeted phishing against instances that have explicitly enabled the password reset feature.
Cross-tenant information disclosure and deletion in Grafana allows a high-privilege authenticated user to read and permanently delete legacy correlation records belonging to
We need to produce a comprehensive JSON analysis for CVE-2026-33212 based on all provided data. We'll synthesize everything into the required fields. Let's gather all details: - CVE ID: CVE-2026-33212 - Description: Weblate, web based localization tool. In versions prior to 5.17, tasks API didn't verify user access for pending tasks. Could expose logs of in-progress operations to unauthorized users. Attacker needs to brute-force random UUID of task, so exploiting is unlikely with default API rate limits. Fixed in version 5.17. - CVSS Score: 3.1, Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N - CWE: CWE-284 (Improper Access Control) - EPSS: 0.03% (percentile 7%) - very low likelihood of exploitation. - Patch: Available from vendor (version 5.17) - CPE: cpe:2.3:a:weblateorg:weblate:*:*:*:*:*:*:*:* (all versions before 5.17?) - Tags: Authentication Bypass, Weblate - SSVC: Exploitation: none, Automatable: no, Technical Impact: partial. So no observed exploitation, not automatable, partial technical impact (info disclosure). - ENISA EUVD: EUVD-2026-22997, affected versions: weblate < 5.17 - References: GHSA advisory, commit, pull request, NVD link. - Source code evidence: GHSA advisory summary (already in description), package pip/weblate vulnerable < 5.17, fixed in 5.17. Commit diff shows addition of task metadata caching and access checks in API views, tests for denied access to inaccessible component, etc. Now, we need to produce a JSON object with all the specified fields. First field: "product_name": "1-3 words ONLY. The specific product or service name affected." Could be "Weblate" or "Weblate localization tool". But product_name should be concise. Weblate is the name. I'll go with "Weblate". "summary": 2-3 sentence plain-language synthesis. Do NOT copy description. Start with specific impact verb and product. "Information disclosure in Weblate's tasks API could expose in-progress operation logs to authenticated users lacking component access if they can guess the task UUID." Or more: "Missing access control in Weblate's tasks API (prior to 5.17) allows low-privileged authenticated users to view logs of pending background tasks by guessing a random UUID, though brute-forcing is mitigated by rate limits. No active exploitation reported, and the vulnerability has a low CVSS score of 3.1." That captures what vulnerability is, who affected (Weblate <5.17), what attacker can do (info disclosure). Also mention EPSS and KEV? KEV not in input (KEV status not provided). So no active exploitation. I'll craft a summary. "technical_context": Explain underlying technology/library/protocol. Weblate is a Django-based web app. The API for tasks (Celery background tasks) uses UUIDs for task IDs. The API view previously extracted related component or translation from task result to perform access check, but for pending tasks the result wasn't available, so it fell back to no access check (or flawed check). The fix uses cached metadata (component ID) to enforce access check even for pending tasks. CWE-284: Improper Access Control. So I'll explain that. "risk_assessment": Assess real-world risk using CVSS, EPSS, KEV (not listed, so no), SSVC, etc. CVSS 3.1 score is LOW: 3.1, with AV:N, AC:H (high complexity due to UUID brute-force), PR:L (low privilege), UI:N, S:U, C:L (low confidentiality impact). EPSS 0.03% (low probability). SSVC: none exploitation, not automatable, partial impact. Not in KEV, no public exploit. So risk is very low. The attack requires authenticated user and brute-force UUID, mitigated by rate limiting. So it's a low-priority issue. "affected_products": Write paragraph listing affected products with versions, CPE if available, and vendor advisory link. "Weblate versions prior to 5.17 are affected. This corresponds to CPE cpe:2.3:a:weblateorg:weblate:*:*:*:*:*:*:*:*. The vendor advisory and fixed version are available at https://github.com/WeblateOrg/weblate/security/advisories/GHSA-vj45-x3pj-f4w4." I'll incorporate the advisory URL. "remediation": Actionable remediation: Upgrade to Weblate 5.17. Since patch is available, primary fix is upgrading. The GHSA advisory says fixed in 5.17. Workaround: ensure API rate limits are in place (default is in place). No other workaround. So paragraph: "Upgrade Weblate to version 5.17 as per vendor advisory at https://github.com/WeblateOrg/weblate/security/advisories/GHSA-vj45-x3pj-f4w4. This release includes the access control fix. As a temporary measure, ensure default API rate limits are enforced, which already make UUID brute-forcing impractical. The commit implementing the fix is at https://github.com/WeblateOrg/weblate/commit/4e06b12cd05d087db68384e09d5f70fe883f2b70." "exploit_scenario": Brief realistic attack scenario: "An authenticated low-privilege user enumerates possible task UUIDs through the tasks API endpoint. For each guess, if the UUID matches a pending task, the API returns task logs that may contain sensitive component data. The attacker brute-forces the UUID, but the default rate limiting significantly hampers this in a real scenario." That's consistent with AC:H. "exploitation_conditions": Extract SPECIFIC, CONCRETE prerequisites. From description: "The attacker needs to brute-force the random UUID of the task, so exploiting this is unlikely with the default API rate limits." So condition is: attacker must authenticate (PR:L, low-privileged) and must successfully guess a valid pending task UUID. The UUID is random, so brute-force required. Additionally, the API rate limits must be insufficient to prevent brute-force. So the exploitation condition is: "Authenticated with low privileges, and must brute-force the random UUID of a pending task; exploitation is mitigated by default API rate limiting." So I'll phrase: "Requires authenticated low-privileged access (PR:L) and the ability to brute-force a random UUID for a pending task; default API rate limits make this impractical." "attack_chain": Steps: Authenticated user sends requests to task detail endpoint with guessed UUIDs → Access control missing for pending tasks → Leak task logs (information disclosure). Short steps: Access as low-privileged user → Guess UUID → Call tasks API endpoint → Receive task logs due to missing access check. Use kill chain phases: Recon → Delivery → Exploit → Impact. But it's a simple chain: "Authenticate with low privileges → Iteratively request task detail with guessed UUID → Exploit missing access control to view pending task logs → Expose in-progress operation details." Compress to 3-7 steps: Authenticate (Access) → Guess UUID (Recon) → Send API request (Delivery) → Missing access check (Exploit) → Retrieve logs (Impact). So I'll produce: "Authenticate with low privilege → Guess random task UUID → Send API request to task detail endpoint → Missing access check exposes task logs → Leak in-progress operation details." That's 5 steps. I'll separate by →. "confidence_notes": What is confirmed? Vendor advisory confirms vulnerability and fix version 5.17. Patch available. No public exploit, no KEV. EUVD confirms. CVSS vector provided. I'll say: "Vulnerability and fix confirmed by vendor advisory (GHSA). No public exploit identified; EPSS probability very low. Affected versions and patch version verified." "prevalence": Weblate is a popular translation tool, but not ubiquitous. It's used by open-source projects for localization. I'd say "medium" prevalence? It's a niche tool but widely used in open-source communities. I'd say "low" because it's specialized, but not rare. However, many open-source projects and some enterprises use it. I'll estimate "medium" (common but not everywhere). Or maybe "low"? I'll consider: Weblate is deployed by projects like KDE, Debian, etc., but it's not as widespread as Tomcat. I'll go with "medium" because it's a well-known tool in localization circles, but not mainstream like WordPress. Balance: prevalence medium. Basis: "widely-used localization platform in open-source communities". I'll justify: "popular web-based localization tool used by many open-source projects". That's "high"? Actually, I'll stick with "medium" because it's not ubiquitous like Linux kernel. "medium" is appropriate. "prevalence_basis": Justification clause: "widely-deployed localization platform in open-source communities". That's plausible. "assessed_cvss_vector": I need to independently assess CVSS vector. Given description, the attack vector is Network (AV:N), attack complexity High (AC:H) due to UUID brute-force, privileges required Low (PR:L) because attacker needs to be authenticated low-privileged user, user interaction None (UI:N), scope Unchanged (S:U), confidentiality impact Low (C:L) because logs may contain some partial info, integrity None (I:N), availability None (A:N). This matches the provided CVSS vector exactly. But I must provide my own, which I would also determine as same. So I'll output "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N". Same. I'll provide rationale: "High complexity due to UUID brute-force, low privilege required, limited information disclosure, consistent with vendor CVSS." But the instruction says "Your OWN independent CVSS 3.1 base-metric vector... grounded in the description... NOT a copy of any score in the input." Since the vector provided is consistent with description, I can provide the same vector, but I must ensure I'm not just copying; I'm deriving it myself. I'll output the vector. However, if there's any discrepancy, I'd adjust. But it seems correct. I'll output it. For "assessed_cvss40_vector": I need to map to CVSS 4.0. The mapping: AV:N -> Network; AC:H -> High; AT:N (no attack requirement needed) because no special conditions beyond brute-force; PR:L -> Low; UI:N -> None; VC:L (confidentiality low) -> Low; VI:N, VA:N; SC:N, SI:N, SA:N (no subsequent system impact). So vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. I'll output that. "assessed_cvss_rationale": "Requires brute-forcing a random UUID, so AC:H; low-privileged authentication, PR:L; only log information disclosed, C:L." Alright, compile JSON. Now, the summary: I need to craft an original synthesis, not copied from description. For example: "Information disclosure in Weblate's tasks API allows authenticated low-privilege users to access logs of in-progress operations if they can guess a pending task's UUID. Fixed in version 5.17, the flaw has a low CVSS score (3.1) and is mitigated by built-in API rate limits, with no active exploitation reported." That's 2-3 sentences. "technical_context": "Weblate is a Django-based translation management system that uses Celery for background tasks. The tasks API endpoint retrieves status and logs for tasks identified by UUID. Prior to version 5.17, the endpoint's permission check relied on the task's result data, which is unavailable for pending tasks, bypassing access control. The flaw (CWE-284) allows any authenticated user to attempt access, but the attacker must brute-force the random UUID. The fix introduced caching of task metadata (component ID) to enforce component-level access checks for pending tasks." "risk_assessment": "The CVSS 3.1 base score is 3.1 (Low), with network attack vector but high complexity due to UUID brute-force, low privileges required, and only limited information disclosure. EPSS probability is 0.03% (7th percentile), indicating very low exploitation likelihood. SSVC decisions note no exploitation observed, automatable: no, technical impact: partial. No public exploits exist, and the vulnerability is not in CISA KEV. The risk is low; exploitation requires significant effort and is
Cross-origin data leak in Google Chrome prior to 147.0.7727.101 through insufficient CORS enforcement when the renderer process is already compromised. An attacker who has first achieved code execution inside the renderer can bypass cross-origin restrictions to expose sensitive data from other origins via a crafted HTML page. No active exploitation or public proof-of-concept has been identified, and the EPSS probability is extremely low at 0.01%.
Cross-origin data leakage in Google Chrome prior to 147.0.7727.101 allows a remote attacker to leak sensitive password data from other origins via a crafted HTML page, but only after they have already compromised the renderer process via a separate exploit. The vulnerability requires user interaction (visiting a malicious page) and has high attack complexity, resulting in a CVSS 3.1 base score of 3.1 (Low severity). No public exploit or active exploitation has been identified at time of analysis, and the EPSS probability is extremely low (0.01%).
Untrusted DLL search path vulnerability in Yubico libfido2 before 1.17.0, python-fido2 before 2.2.0, and yubikey-manager before 5.9.1 allows local attackers to achieve privilege escalation or code execution by placing a malicious DLL in a directory searched before the legitimate library location. The vulnerability requires local access and high complexity conditions but affects three widely-used FIDO2 authentication libraries; no public exploit code identified at time of analysis.
HCL AION allows local attackers with high privileges to explore internal filesystem structures through certain system behaviors, potentially disclosing information about the underlying environment that could facilitate further targeted attacks. The vulnerability requires local access, high privileges, and user interaction to trigger, with a CVSS score of 2.9 reflecting low immediate risk. No public exploit code or active exploitation has been identified.
Mattermost versions 10.11.0 through 10.11.12 fail to validate workspace ownership during Connected Workspaces API interactions, allowing a malicious remote server with high privileges to modify the displayed status of local users. This affects organizations using the Connected Workspaces federation feature and requires an attacker to already possess high administrative privileges on a connected remote instance. The vulnerability has CVSS 2.7 (low severity) and no public exploit code or active exploitation has been identified.
Information disclosure in Grafana Alerting allows users with the 'Contact Point Writer' role (part of Editor role) to extract redacted credentials from third-party integrations. By editing a contact point's endpoint URL to an attacker-controlled server and invoking the test function, redacted settings such as Slack tokens are sent to the attacker. Affected versions are Grafana Alerting 8.0.0 through 12.3.0; no public exploit or active exploitation identified, and the EPSS score is very low (0.04%).