deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-rvqx-wpfh-mfx7
Package: langflow (PIP)
Severity: CRITICAL (CVSS 0.0)
CWE: CWE-94: Improper Control of Generation of Code ('Code Injection')
Vulnerable versions: < 1.3.0
Patched in: 1.3.0

Summary: Langflow Unauth RCE

Details:
Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.
GitHub Security Advisory: GHSA-7pr5-w74r-jjj7
Package: Mezzanine (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: < 6.1.1
Patched in: 6.1.1

Summary: Mezzanine CMS has a Stored Cross-Site Scripting (XSS) vulnerability in the displayable_links_js function

Details:
Mezzanine CMS, in versions prior to 6.1.1, contains a Stored Cross-Site Scripting (XSS) vulnerability in the admin interface. The vulnerability exists in the "displayable_links_js" function, which fails to properly sanitize blog post titles before including them in JSON responses served via "/admin/displayable_links.js". An authenticated admin user can create a blog post with a malicious JavaScript payload in the title field, then trick another admin user into clicking a direct link to the "/admin/displayable_links.js" endpoint, causing the malicious script to execute in their browser.
GitHub Security Advisory: GHSA-rp38-pj7h-r8q2
Package: python-a2a (PIP)
Severity: MODERATE (CVSS 5.5)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: < 0.5.6
Patched in: 0.5.6

Summary: python-a2a has a path traversal in the create_workflow function

Details:
A vulnerability classified as critical has been found in themanojdesai python-a2a up to 0.5.5. Affected is the function create_workflow of the file python_a2a/agent_flow/server/api.py. The manipulation leads to path traversal. Upgrading to version 0.5.6 is able to address this issue. It is recommended to upgrade the affected component.
GitHub Security Advisory: GHSA-5qpg-rh4j-qp35
Package: pycares (PIP)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-416: Use After Free
Vulnerable versions: <= 4.8.0
Patched in: 4.9.0

Summary: pycares has a Use-After-Free Vulnerability

Details:
## Summary

pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash.

## Details

### Root Cause

The vulnerability stems from improper handling of callback references when the Channel object is destroyed:

1. When a DNS query is initiated, pycares stores a callback reference using `ffi.new_handle()`
2. If the Channel object is garbage collected while queries are pending, the callback references become invalid
3. When c-ares attempts to invoke the callback, it accesses freed memory, causing a fatal error

This issue was much more likely to occur when using `event_thread=True` but could happen without it under the right circumstances.

### Technical Details

The core issue is a race condition between Python's garbage collector and c-ares's callback execution:

1. When `__del__` is called from within a c-ares callback context, we cannot immediately call `ares_destroy()` because c-ares is still executing code after the callback returns
2. c-ares needs to execute cleanup code after our Python callback returns (specifically at lines 1422-1429 in ares_process.c)
3. If we destroy the channel too quickly, c-ares accesses freed memory

### Impact

Applications using `pycares` can be crashed remotely by triggering DNS queries that result in `Channel` objects being garbage collected before query completion. This is particularly problematic in scenarios where:

- Channel objects are created per-request
- Multiple failed DNS queries are processed rapidly
- The application doesn't properly manage Channel lifecycle

The error manifests as:
```
Fatal Python error: b_from_handle: ffi.from_handle() detected that the address passed points to garbage
```

## Fix

The vulnerability has been fixed in pycares 4.9.0 by implementing a safe channel destruction mechanism

## Mitigation

### For Application Developers

1. **Upgrade to pycares >= 4.9.0** - This version includes the fix and requires no code changes
2. **Best practices** (optional but recommended):
   ```python
   # Explicit cleanup
   channel.close()
   
   # Or use context manager
   with pycares.Channel() as channel:
       # ... use channel ...
   # Automatically closed
   ```
3. **Avoid creating Channel objects per-request** - Prefer long-lived instances for better performance and safety

The fix is completely transparent - no API changes or code modifications are required.

## Credit

This vulnerability was reported by @vEpiphyte through the aio-libs security program.
GitHub Security Advisory: GHSA-8qvm-5x2c-j2w7
Package: protobuf (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-674: Uncontrolled Recursion
Vulnerable versions: >= 6.30.0rc1, < 6.31.1
Patched in: 6.31.1

Summary: protobuf-python has a potential Denial of Service issue

Details:
### Summary
Any project that uses Protobuf pure-Python backend to parse untrusted Protocol Buffers data containing an arbitrary number of **recursive groups**, **recursive messages** or **a series of [`SGROUP`](https://protobuf.dev/programming-guides/encoding/#groups) tags** can be corrupted by exceeding the Python recursion limit.

Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
[ecosystem@trailofbits.com](mailto:ecosystem@trailofbits.com)

Affected versions: This issue only affects the [pure-Python implementation](https://github.com/protocolbuffers/protobuf/tree/main/python#implementation-backends) of protobuf-python backend. This is the implementation when `PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python` environment variable is set or the default when protobuf is used from Bazel or pure-Python PyPi wheels. CPython PyPi wheels do not use pure-Python by default.

This is a Python variant of a [previous issue affecting protobuf-java](https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-735f-pc8j-v9w8).

### Severity
This is a potential Denial of Service. Parsing nested protobuf data creates unbounded recursions that can be abused by an attacker.

### Proof of Concept
For reproduction details, please refer to the unit tests [decoder_test.py](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/decoder_test.py#L87-L98) and [message_test](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/message_test.py#L1436-L1478)

### Remediation and Mitigation
A mitigation is available now. Please update to the latest available versions of the following packages:
* protobuf-python(4.25.8, 5.29.5, 6.31.1)
GitHub Security Advisory: GHSA-8qvm-5x2c-j2w7
Package: protobuf (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-674: Uncontrolled Recursion
Vulnerable versions: >= 5.26.0rc1, < 5.29.5
Patched in: 5.29.5

Summary: protobuf-python has a potential Denial of Service issue

Details:
### Summary
Any project that uses Protobuf pure-Python backend to parse untrusted Protocol Buffers data containing an arbitrary number of **recursive groups**, **recursive messages** or **a series of [`SGROUP`](https://protobuf.dev/programming-guides/encoding/#groups) tags** can be corrupted by exceeding the Python recursion limit.

Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
[ecosystem@trailofbits.com](mailto:ecosystem@trailofbits.com)

Affected versions: This issue only affects the [pure-Python implementation](https://github.com/protocolbuffers/protobuf/tree/main/python#implementation-backends) of protobuf-python backend. This is the implementation when `PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python` environment variable is set or the default when protobuf is used from Bazel or pure-Python PyPi wheels. CPython PyPi wheels do not use pure-Python by default.

This is a Python variant of a [previous issue affecting protobuf-java](https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-735f-pc8j-v9w8).

### Severity
This is a potential Denial of Service. Parsing nested protobuf data creates unbounded recursions that can be abused by an attacker.

### Proof of Concept
For reproduction details, please refer to the unit tests [decoder_test.py](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/decoder_test.py#L87-L98) and [message_test](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/message_test.py#L1436-L1478)

### Remediation and Mitigation
A mitigation is available now. Please update to the latest available versions of the following packages:
* protobuf-python(4.25.8, 5.29.5, 6.31.1)
GitHub Security Advisory: GHSA-8qvm-5x2c-j2w7
Package: protobuf (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-674: Uncontrolled Recursion
Vulnerable versions: < 4.25.8
Patched in: 4.25.8

Summary: protobuf-python has a potential Denial of Service issue

Details:
### Summary
Any project that uses Protobuf pure-Python backend to parse untrusted Protocol Buffers data containing an arbitrary number of **recursive groups**, **recursive messages** or **a series of [`SGROUP`](https://protobuf.dev/programming-guides/encoding/#groups) tags** can be corrupted by exceeding the Python recursion limit.

Reporter: Alexis Challande, Trail of Bits Ecosystem Security Team
[ecosystem@trailofbits.com](mailto:ecosystem@trailofbits.com)

Affected versions: This issue only affects the [pure-Python implementation](https://github.com/protocolbuffers/protobuf/tree/main/python#implementation-backends) of protobuf-python backend. This is the implementation when `PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python` environment variable is set or the default when protobuf is used from Bazel or pure-Python PyPi wheels. CPython PyPi wheels do not use pure-Python by default.

This is a Python variant of a [previous issue affecting protobuf-java](https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-735f-pc8j-v9w8).

### Severity
This is a potential Denial of Service. Parsing nested protobuf data creates unbounded recursions that can be abused by an attacker.

### Proof of Concept
For reproduction details, please refer to the unit tests [decoder_test.py](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/decoder_test.py#L87-L98) and [message_test](https://github.com/protocolbuffers/protobuf/blob/main/python/google/protobuf/internal/message_test.py#L1436-L1478)

### Remediation and Mitigation
A mitigation is available now. Please update to the latest available versions of the following packages:
* protobuf-python(4.25.8, 5.29.5, 6.31.1)
GitHub Security Advisory: GHSA-4qqf-9m5c-w2c5
Package: weblate (PIP)
Severity: LOW (CVSS 5.3)
CWE: CWE-359: Exposure of Private Personal Information to an Unauthorized Actor
Vulnerable versions: < 5.12
Patched in: 5.12

Summary: Weblate exposes personal IP address via e-mail

Details:
### Impact

The audit log notifications included the full IP address of the acting user. This could be obtained by third-party servers such as SMTP relays, or spam filters.

### Patches

This issue has been addressed in Weblate 5.12 via https://github.com/WeblateOrg/weblate/pull/15102.

### References

Thanks to [micael1](https://hackerone.com/micael1) for reporting this [issue at HackerOne](https://hackerone.com/reports/3179850).
GitHub Security Advisory: GHSA-57jg-m997-cx3q
Package: weblate (PIP)
Severity: MODERATE (CVSS 4.9)
CWE: CWE-307: Improper Restriction of Excessive Authentication Attempts
Vulnerable versions: < 5.12
Patched in: 5.12

Summary: Weblate lacks rate limiting when verifying second factor

Details:
### Impact

The verification of the second factor was not subject to rate limiting. The absence of rate limiting on the second factor endpoint allows an attacker with valid credentials to automate OTP guessing. 

### Patches

This issue has been addressed in Weblate 5.12 via https://github.com/WeblateOrg/weblate/pull/14918.

### References

Thanks to [obscuredeer](https://hackerone.com/obscuredeer) for reporting this [issue at HackerOne](https://hackerone.com/reports/3150564).
GitHub Security Advisory: GHSA-8pcp-r83j-fc92
Package: salt (PIP)
Severity: CRITICAL (CVSS 9.6)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt vulnerable to directory traversal attack in file receiving method

Details:
Directory traversal vulnerability in recv_file method allows arbitrary files to be written to the master cache directory.
GitHub Security Advisory: GHSA-8pcp-r83j-fc92
Package: salt (PIP)
Severity: CRITICAL (CVSS 9.6)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt vulnerable to directory traversal attack in file receiving method

Details:
Directory traversal vulnerability in recv_file method allows arbitrary files to be written to the master cache directory.
GitHub Security Advisory: GHSA-989c-m532-p2hv
Package: salt (PIP)
Severity: MODERATE (CVSS 5.6)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt's worker process vulnerable to denial of service through file read operation

Details:
Worker process denial of service through file read operation. .A vulnerability exists in the Master's “pub_ret” method which is exposed to all minions. The un-sanitized input value “jid” is used to construct a path which is then opened for reading. An attacker could exploit this vulnerabilities by attempting to read from a filename that will not return any data, e.g. by targeting a pipe node on the proc file system.
GitHub Security Advisory: GHSA-989c-m532-p2hv
Package: salt (PIP)
Severity: MODERATE (CVSS 5.6)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt's worker process vulnerable to denial of service through file read operation

Details:
Worker process denial of service through file read operation. .A vulnerability exists in the Master's “pub_ret” method which is exposed to all minions. The un-sanitized input value “jid” is used to construct a path which is then opened for reading. An attacker could exploit this vulnerabilities by attempting to read from a filename that will not return any data, e.g. by targeting a pipe node on the proc file system.
GitHub Security Advisory: GHSA-7f3f-x5f5-79gw
Package: salt (PIP)
Severity: MODERATE (CVSS 5.6)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-73: External Control of File Name or Path
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt's file contents overwrite the VirtKey class

Details:
File contents overwrite the VirtKey class is called when “on-demand pillar” data is requested and uses un-validated input to create paths to the “pki directory”. The functionality is used to auto-accept Minion authentication keys based on a pre-placed “authorization file” at a specific location and is present in the default configuration.
GitHub Security Advisory: GHSA-7f3f-x5f5-79gw
Package: salt (PIP)
Severity: MODERATE (CVSS 5.6)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-73: External Control of File Name or Path
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt's file contents overwrite the VirtKey class

Details:
File contents overwrite the VirtKey class is called when “on-demand pillar” data is requested and uses un-validated input to create paths to the “pki directory”. The functionality is used to auto-accept Minion authentication keys based on a pre-placed “authorization file” at a specific location and is present in the default configuration.
GitHub Security Advisory: GHSA-xh32-3m67-qjgf
Package: salt (PIP)
Severity: MODERATE (CVSS 6.3)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt allows arbitrary directory creation or file deletion

Details:
Arbitrary directory creation or file deletion. In the find_file method of the GitFS class, a path is created using os.path.join using unvalidated input from the “tgt_env” variable. This can be exploited by an attacker to delete any file on the Master's process has permissions to.
GitHub Security Advisory: GHSA-xh32-3m67-qjgf
Package: salt (PIP)
Severity: MODERATE (CVSS 6.3)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt allows arbitrary directory creation or file deletion

Details:
Arbitrary directory creation or file deletion. In the find_file method of the GitFS class, a path is created using os.path.join using unvalidated input from the “tgt_env” variable. This can be exploited by an attacker to delete any file on the Master's process has permissions to.
GitHub Security Advisory: GHSA-c46w-gr7f-jm2p
Package: salt (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-285: Improper Authorization
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt vulnerable to arbitrary event injection

Details:
Arbitrary event injection on Salt Master. The master's "_minion_event" method can be used by and authorized minion to send arbitrary events onto the master's event bus.
GitHub Security Advisory: GHSA-c46w-gr7f-jm2p
Package: salt (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-285: Improper Authorization
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt vulnerable to arbitrary event injection

Details:
Arbitrary event injection on Salt Master. The master's "_minion_event" method can be used by and authorized minion to send arbitrary events onto the master's event bus.
GitHub Security Advisory: GHSA-r546-h3ff-q585
Package: salt (PIP)
Severity: MODERATE (CVSS 4.2)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt vulnerable to directory traversal attack in minion file cache creation

Details:
Directory traversal attack in minion file cache creation. The master's default cache is vulnerable to a directory traversal attack. Which could be leveraged to write or overwrite 'cache' files outside of the cache directory.
GitHub Security Advisory: GHSA-r546-h3ff-q585
Package: salt (PIP)
Severity: MODERATE (CVSS 4.2)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt vulnerable to directory traversal attack in minion file cache creation

Details:
Directory traversal attack in minion file cache creation. The master's default cache is vulnerable to a directory traversal attack. Which could be leveraged to write or overwrite 'cache' files outside of the cache directory.
GitHub Security Advisory: GHSA-fcr4-h6c4-rvvp
Package: salt (PIP)
Severity: MODERATE (CVSS 6.7)
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt's on demand pillar functionality vulnerable to arbitrary command injections 

Details:
An attacker with access to a minion key can exploit the 'on demand' pillar functionality with a specially crafted git url which could cause and arbitrary command to be run on the master with the same privileges as the master process.
GitHub Security Advisory: GHSA-fcr4-h6c4-rvvp
Package: salt (PIP)
Severity: MODERATE (CVSS 6.7)
CWE: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt's on demand pillar functionality vulnerable to arbitrary command injections 

Details:
An attacker with access to a minion key can exploit the 'on demand' pillar functionality with a specially crafted git url which could cause and arbitrary command to be run on the master with the same privileges as the master process.
GitHub Security Advisory: GHSA-jh7c-xh74-h76f
Package: salt (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 3006.0, < 3006.12
Patched in: 3006.12

Summary: Salt has minion event bus authorization bypass vulnerability

Details:
Minion event bus authorization bypass. An attacker with access to a minion key can craft a message which may be able to execute a job on other minions (>= 3007.0).
GitHub Security Advisory: GHSA-jh7c-xh74-h76f
Package: salt (PIP)
Severity: HIGH (CVSS 8.1)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 3007.0, < 3007.4
Patched in: 3007.4

Summary: Salt has minion event bus authorization bypass vulnerability

Details:
Minion event bus authorization bypass. An attacker with access to a minion key can craft a message which may be able to execute a job on other minions (>= 3007.0).
GitHub Security Advisory: GHSA-4j59-vv55-q6h3
Package: salt (PIP)
Severity: MODERATE (CVSS 6.4)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 3007.0rc1, < 3007.4
Patched in: 3007.4

Summary: Salt's salt.auth.pki module does not properly authenticate callers

Details:
The salt.auth.pki module does not properly authenticate callers. The "password" field contains a public certificate which is validated against a CA certificate by the module. This is not pki authentication, as the caller does not need access to the corresponding private key for the authentication attempt to be accepted.
GitHub Security Advisory: GHSA-4j59-vv55-q6h3
Package: salt (PIP)
Severity: MODERATE (CVSS 6.4)
CWE: CWE-287: Improper Authentication
Vulnerable versions: >= 3006.0rc1, < 3006.12
Patched in: 3006.12

Summary: Salt's salt.auth.pki module does not properly authenticate callers

Details:
The salt.auth.pki module does not properly authenticate callers. The "password" field contains a public certificate which is validated against a CA certificate by the module. This is not pki authentication, as the caller does not need access to the corresponding private key for the authentication attempt to be accepted.
GitHub Security Advisory: GHSA-m3mq-f375-5vgh
Package: vantage6-server (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: < 4.11.0
Patched in: 4.11.0

Summary: Vantage6 Server JWT secret not cryptographically secure

Details:
### Impact
The JWT secret key in the vantage6 server is auto-generated unless defined by the user. The auto-generated key is a UUID1, which is not cryptographically secure as it is [predictable to some extent](https://docs.python.org/3/library/uuid.html#uuid.uuid1)

### Patches
No

### Workarounds
You may define JWT secret key in the server configuration file
GitHub Security Advisory: GHSA-j6g5-p62x-58hw
Package: vantage6 (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-307: Improper Restriction of Excessive Authentication Attempts
Vulnerable versions: < 4.11.0
Patched in: 4.11.0

Summary: vantage6 lacks brute-force protection on change password functionality

Details:
### Impact
If attacker gets access to an authenticated session, they can try to brute-force the user password by using the change password functionality: they can call that route infinitely which will return the message that password is wrong until it is correct

### Patches
This issue has been patched in version 4.11.0

### Workarounds
None