deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-r6h4-mm7h-8pmq
Package: pymdown-extensions (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-1333: Inefficient Regular Expression Complexity
Vulnerable versions: < 10.16.1
Patched in: 10.16.1

Summary: PyMdown Extensions has a ReDOS bug in its Figure Capture extension

Details:
### Impact

This issue describes a ReDOS bug found within the figure caption extension (`pymdownx.blocks.caption` ).

In systems that take unchecked user content, this could cause long hangs when processing the data if a malicious payload was crafted.

### Patches

This issue is patched in Release [10.16.1](https://pypi.org/project/pymdown-extensions/10.16.1/).

### Workarounds

Some possible workarounds

If users are concerned about this vulnerability and process unknown user content without timeouts or other safeguards in place to prevent really large, malicious content being aimed at systems, the use of `pymdownx.blocks.caption` could be avoided until the library is updated to 10.16.1+.

### References

The original issue https://github.com/facelessuser/pymdown-extensions/issues/2716.

### Description

The original issue came through PyMdown Extensions' normal issue tracker instead of the typical security flow: https://github.com/facelessuser/pymdown-extensions/issues/2716. Because this came through the normal issue flow, it was handled as a normal issue. In the future, PyMdown Extensions will ensure such issues, even if prematurely made public through the normal issue flow, are redirected through the typical security process.

The regular expression pattern in question is as follows:

```py
RE_FIG_NUM = re.compile(r'^(\^)?([1-9][0-9]*(?:.[1-9][0-9]*)*)(?= |$)')
```

The POC was provided by @ShangzhiXu

```py
import re
import time

regex_pattern = re.compile(r'^(\^)?([1-9][0-9]*(?:.[1-9][0-9]*)*)(?= |$)')

for i in range(50, 500, 50):
    long_string = '1' * i + 'a'
    start_time = time.time()
    match = re.match(regex_pattern, long_string)
    end_time = time.time()
    print(f"long_string execution time: {end_time - start_time:.6f} s")
```

The issue with the above pattern is that `.` was used, which accepts any character when we meant to use `\.`. The fix was to update the pattern to:

```py
RE_FIG_NUM = re.compile(r'^(\^)?([1-9][0-9]*(?:\.[1-9][0-9]*)*)(?= |$)')
```

Relevant PR with fix: https://github.com/facelessuser/pymdown-extensions/pull/2717

### Version(s) & System Info

- Operating System: Any
- Python Version: Any
GitHub Security Advisory: GHSA-8m3c-c723-h4p4
Package: django-allauth (PIP)
Severity: MODERATE (CVSS 5.4)
CWE: CWE-287: Improper Authentication
Vulnerable versions: < 65.13.0
Patched in: 65.13.0

Summary: django-allauth's Okta and NetIQ implementations used a mutable identifier for authorization decisions

Details:
An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.
GitHub Security Advisory: GHSA-qhmc-3mvr-f2j4
Package: django-allauth (PIP)
Severity: MODERATE (CVSS 5.4)
CWE: CWE-613: Insufficient Session Expiration
Vulnerable versions: < 65.13.0
Patched in: 65.13.0

Summary: django-allauth does not reject access tokens for inactive users

Details:
An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as is_active=False after having handed tokens for that user while the account was still active had no effect. Fixed the access/refresh tokens are now rejected.
GitHub Security Advisory: GHSA-fv47-pqh6-wxgq
Package: apache-airflow (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-201: Insertion of Sensitive Information Into Sent Data
Vulnerable versions: >= 3.1.0, < 3.1.4
Patched in: 3.1.5

Summary: Apache Airflow exposes secret values to authenticated UI users via rendered templates

Details:
A vulnerability in Apache Airflow allowed authenticated UI users to view secret values in rendered templates due to secrets not being properly redacted, potentially exposing secrets to users without the appropriate authorization.

Users are recommended to upgrade to version 3.1.4, which fixes this issue.
GitHub Security Advisory: GHSA-x37w-7p52-8f49
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: < 4.6.12
Patched in: 4.6.12

Summary: Mayan EDMS has an Open Redirect through the /authentication/ file

Details:
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-x37w-7p52-8f49
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 4.7.0, < 4.7.8
Patched in: 4.7.8

Summary: Mayan EDMS has an Open Redirect through the /authentication/ file

Details:
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-x37w-7p52-8f49
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 4.8.0, < 4.8.10
Patched in: 4.8.10

Summary: Mayan EDMS has an Open Redirect through the /authentication/ file

Details:
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-x37w-7p52-8f49
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 4.9.0, < 4.9.7
Patched in: 4.9.7

Summary: Mayan EDMS has an Open Redirect through the /authentication/ file

Details:
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-x37w-7p52-8f49
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Vulnerable versions: >= 4.10.0, < 4.10.2
Patched in: 4.10.2

Summary: Mayan EDMS has an Open Redirect through the /authentication/ file

Details:
A flaw has been found in Mayan EDMS up to 4.10.1. The impacted element is an unknown function of the file /authentication/. This manipulation causes open redirect. It is possible to initiate the attack remotely. The exploit has been published and may be used. Upgrading to version 4.10.2 is sufficient to resolve this issue. The affected component should be upgraded. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-774q-r975-vqwp
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 4.6.12
Patched in: 4.6.12

Summary: Mayan EDMS is vulnerable to XSS through the /authentication/ file

Details:
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. Users should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-774q-r975-vqwp
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 4.7.0, < 4.7.8
Patched in: 4.7.8

Summary: Mayan EDMS is vulnerable to XSS through the /authentication/ file

Details:
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. Users should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-774q-r975-vqwp
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 4.8.0, < 4.8.10
Patched in: 4.8.10

Summary: Mayan EDMS is vulnerable to XSS through the /authentication/ file

Details:
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. Users should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-774q-r975-vqwp
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 4.9.0, < 4.9.7
Patched in: 4.9.7

Summary: Mayan EDMS is vulnerable to XSS through the /authentication/ file

Details:
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. Users should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-774q-r975-vqwp
Package: mayan-edms (PIP)
Severity: LOW (CVSS 4.3)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 4.10.0, < 4.10.2
Patched in: 4.10.2

Summary: Mayan EDMS is vulnerable to XSS through the /authentication/ file

Details:
A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. Users should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."
GitHub Security Advisory: GHSA-6gvq-jcmp-8959
Package: altcha (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-115: Misinterpretation of Input, CWE-347: Improper Verification of Cryptographic Signature
Vulnerable versions: < 1.0.0
Patched in: 1.0.0

Summary: ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay

Details:
### Impact

A cryptographic semantic binding flaw in ALTCHA libraries allows challenge payload splicing, which may enable replay attacks. The HMAC signature does not unambiguously bind challenge parameters to the nonce, allowing an attacker to reinterpret a valid proof-of-work submission with a modified expiration value. This may allow previously solved challenges to be reused beyond their intended lifetime, depending on server-side replay handling and deployment assumptions.

The vulnerability primarily impacts abuse-prevention mechanisms such as rate limiting and bot mitigation. It does not directly affect data confidentiality or integrity. 

### Patches

This issue has been addressed by enforcing explicit semantic separation between challenge parameters and the nonce during HMAC computation.

Users are advised to upgrade to patched versions.

### Workarounds

As a mitigation, implementations may append a delimiter to the end of the `salt` value prior to HMAC computation (for example, `<salt>?expires=<time>&`). This prevents ambiguity between parameters and the nonce and is backward-compatible with existing implementations, as the delimiter is treated as a standard URL parameter separator.
GitHub Security Advisory: GHSA-75mj-4g74-9rg2
Package: utcp (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-501: Trust Boundary Violation
Vulnerable versions: < 1.1.0
Patched in: 1.1.0

Summary: Universal Tool Calling Protocol (UTCP) client library for Python vulnerable to Trust Boundary Violation through Manual JSON specification

Details:
The vulnerability arises when a client fetches a tools’ JSON specification, known as a Manual, from a remote Manual Endpoint. While a provider may initially serve a benign manual (e.g., one defining an HTTP tool call), earning the clients’ trust, a malicious provider can later change the manual to exploit the client.
GitHub Security Advisory: GHSA-3pmh-24wp-xpf4
Package: Weblate (PIP)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-284: Improper Access Control, CWE-285: Improper Authorization
Vulnerable versions: < 5.15
Patched in: 5.15

Summary: Weblate has Systematic User and Project Enumeration via Broken Authorization in REST API (IDOR)

Details:
### Impact

It was possible to retrieve user notification settings or list all users via API.

### Patches

* https://github.com/WeblateOrg/weblate/pull/17256

### References

Thanks to Hector Ruiz Ruiz & NaxusAI for responsibly disclosing this vulnerability to Weblate.
GitHub Security Advisory: GHSA-pj86-258h-qrvf
Package: Weblate (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-1286: Improper Validation of Syntactic Correctness of Input
Vulnerable versions: < 5.15
Patched in: 5.15

Summary: Weblate's over‑permissive webhook endpoint enables mass repository updates and component enumeration

Details:
### Impact

It was possible to trigger repository updates for many repositories via a crafted webhook payload.

### Patches

* https://github.com/WeblateOrg/weblate/pull/17221

### Workarounds

Disabling webhooks completely using ENABLE_HOOKS avoids this vulnerability.

### References

Thanks to Hector Ruiz Ruiz & NaxusAI for responsibly disclosing this vulnerability to us.
GitHub Security Advisory: GHSA-m6hq-f4w9-qrjj
Package: Weblate (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-286: Incorrect User Management
Vulnerable versions: < 5.15
Patched in: 5.15

Summary: Weblate has improper validation upon invitation acceptance

Details:
### Impact

It was possible to accept an invitation opened by a different Weblate user.

### Patches

* https://github.com/WeblateOrg/weblate/pull/16913

### Workarounds

Users should avoid leaving Weblate sessions with an unattended opened invitation.

### References

Thanks to Nahid0x for responsibly disclosing this vulnerability to Weblate.
GitHub Security Advisory: GHSA-fxmw-jcgr-w44v
Package: pgadmin4 (PIP)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: < 9.11
Patched in: 9.11

Summary: pgadmin4 has a Meta-Command Filter Command Execution

Details:
The PLAIN restore meta-command filter introduced in pgAdmin as part of the fix for CVE-2025-12762 does not detect meta-commands when a SQL file begins with a UTF-8 Byte Order Mark (EF BB BF) or other special byte sequences. The implemented filter uses the function `has_meta_commands()`, which scans raw bytes using a regular expression. The regex does not treat the bytes as ignorable, so meta-commands such as `\\!` remain undetected. When pgAdmin invokes psql with --file, psql strips the bytes and executes the command. This can result in remote command execution during a restore operation.
GitHub Security Advisory: GHSA-wx63-35hw-2482
Package: mad-proxy (PIP)
Severity: MODERATE (CVSS 5.3)
CWE: CWE-693: Protection Mechanism Failure
Vulnerable versions: <= 0.3
Patched in: unpatched

Summary: HTTP/HTTPS Traffic Interception Bypass in mad-proxy

Details:
A vulnerability in mad-proxy versions <= 0.3 allows attackers to bypass HTTP/HTTPS traffic interception rules, potentially exposing sensitive traffic.
GitHub Security Advisory: GHSA-2m4f-cg75-76w2
Package: nicegui (PIP)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: <= 3.3.1
Patched in: 3.4.0

Summary: NiceGUI Stored/Reflected XSS in ui.interactive_image via unsanitized SVG content

Details:
### Summary
A Cross-Site Scripting (XSS) vulnerability exists in the `ui.interactive_image` component of NiceGUI (v3.3.1 and earlier). The component renders SVG content using Vue's `v-html` directive without any sanitization. This allows attackers to inject malicious HTML or JavaScript via the SVG `<foreignObject>` tag.

### Details
The vulnerability is located in `nicegui/elements/interactive_image.js`.
The component uses the following code to render content:
```javascript
<g v-html="content"></g>
```
Vue's v-html directive renders raw HTML strings into the DOM. If an application allows user-controlled input to be passed to the content property of an interactive image, an attacker can embed a <foreignObject> tag containing malicious scripts, bypassing typical image restrictions.

### PoC
```python
from nicegui import ui

@ui.page('/')
def main():
    ui.label('NiceGUI SVG XSS PoC')
    
    # Standard image loading
    img = ui.interactive_image('[https://picsum.photos/640/360](https://picsum.photos/640/360)')
    
    # Payload: Embeds raw HTML execution inside SVG
    # This executes immediately when the image component is rendered
    img.content = (
        '<foreignObject>'
        '<body xmlns="[http://www.w3.org/1999/xhtml](http://www.w3.org/1999/xhtml)">'
        '<img src=x onerror=alert("XSS-SVG")>'
        '</body>'
        '</foreignObject>'
    )

ui.run()
```

### Impact
- Type: Reflected / Stored XSS (depending on data source)

- Severity: Moderate

- Impact: Attackers can inject malicious scripts that execute whenever the image component is rendered or updated. This is particularly dangerous for dashboards or multi-user applications displaying user-generated content or annotations.
GitHub Security Advisory: GHSA-72qc-wxch-74mg
Package: nicegui (PIP)
Severity: MODERATE (CVSS 6.1)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: <= 3.3.1
Patched in: 3.4.0

Summary: NiceGUI Reflected XSS in ui.add_css, ui.add_scss, and ui.add_sass via Style Injection

Details:
### Summary
A Cross-Site Scripting (XSS) vulnerability exists in `ui.add_css`, `ui.add_scss`, and `ui.add_sass` functions in NiceGUI (v3.3.1 and earlier).

These functions allow developers to inject styles dynamically. However, they lack proper sanitization or encoding for the JavaScript context they generate. An attacker can break out of the intended `<style>` or `<script>` tags by injecting closing tags (e.g., `</style>` or `</script>`), allowing for the execution of arbitrary JavaScript.

### Details
The vulnerability stems from how these functions inject content into the DOM using `client.run_javascript` (or `add_head_html` internally) without sufficient escaping for the transport layer.

* **`ui.add_css`**: Injects content into a `<style>` tag. Input containing `</style>` closes the tag prematurely, allowing subsequent HTML/JS injection.
* **`ui.add_scss` / `ui.add_sass`**: These rely on client-side compilation within `<script>` tags. Input containing `</script>` breaks the execution context, allowing XSS.

### PoC
**Scenario:** A developer allows users to customize a theme color via a URL parameter.

```python
from nicegui import ui

@ui.page('/')
def main(color: str = 'blue'):
    # Vulnerable implementation of dynamic theming
    ui.add_css(f'.q-btn {{ background-color: {color} !important; }}')
    ui.button('Click Me')

ui.run(port=8082)
```
**Attack Vector:**
Accessing the following URL executes arbitrary JavaScript:
`http://localhost:8082/?color=red;}</style><img src=x onerror=alert(document.domain)><style>`

### Impact
* **Type:** Reflected XSS
* **Severity:** Moderate 
* **Affected Components:** Applications using `ui.add_css`, `ui.add_scss`, or `ui.add_sass` with untrusted input (e.g., dynamic theming based on user input).
GitHub Security Advisory: GHSA-8ggh-xwr9-3373
Package: ansible (PIP)
Severity: MODERATE (CVSS 5.5)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, CWE-532: Insertion of Sensitive Information into Log File
Vulnerable versions: < 12.2.0
Patched in: 12.2.0

Summary: Ansible Community General Collection is vulnerable to exposure of sensitive information

Details:
A flaw was found in ansible-collection-community-general. This vulnerability allows for information exposure (IE) of sensitive credentials, specifically plaintext passwords, via verbose output when running Ansible with debug modes. Attackers with access to logs could retrieve these secrets and potentially compromise Keycloak accounts or administrative access.
GitHub Security Advisory: GHSA-5cvj-7rg6-jggj
Package: mlflow (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 2.22.4
Patched in: 2.22.4

Summary: MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability

Details:
MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MLflow Tracking Server. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of model file paths. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-26921.