deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-mmwr-2jhp-mc7j
Package: Django (PIP)
Severity: LOW (CVSS 2.7)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 4.2, < 4.2.30
Patched in: 4.2.30

Summary: Django vulnerable to privilege abuse in ModelAdmin.list_editable

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Cantina for reporting this issue.
GitHub Security Advisory: GHSA-mmwr-2jhp-mc7j
Package: Django (PIP)
Severity: LOW (CVSS 2.7)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 5.2, < 5.2.13
Patched in: 5.2.13

Summary: Django vulnerable to privilege abuse in ModelAdmin.list_editable

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Cantina for reporting this issue.
GitHub Security Advisory: GHSA-mmwr-2jhp-mc7j
Package: Django (PIP)
Severity: LOW (CVSS 2.7)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 6.0, < 6.0.4
Patched in: 6.0.4

Summary: Django vulnerable to privilege abuse in ModelAdmin.list_editable

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Admin changelist forms using `ModelAdmin.list_editable` incorrectly allowed new instances to be created via forged `POST` data.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Cantina for reporting this issue.
GitHub Security Advisory: GHSA-pwjp-ccjc-ghwg
Package: Django (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 4.2, < 4.2.30
Patched in: 4.2.30

Summary: Django vulnerable to privilege abuse in GenericInlineModelAdmin

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank N05ec@LZU-DSLab for reporting this issue.
GitHub Security Advisory: GHSA-pwjp-ccjc-ghwg
Package: Django (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 5.2, < 5.2.13
Patched in: 5.2.13

Summary: Django vulnerable to privilege abuse in GenericInlineModelAdmin

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank N05ec@LZU-DSLab for reporting this issue.
GitHub Security Advisory: GHSA-pwjp-ccjc-ghwg
Package: Django (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 6.0, < 6.0.4
Patched in: 6.0.4

Summary: Django vulnerable to privilege abuse in GenericInlineModelAdmin

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. Add permissions on inline model instances were not validated on submission of forged `POST` data in `GenericInlineModelAdmin`.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank N05ec@LZU-DSLab for reporting this issue.
GitHub Security Advisory: GHSA-mvfq-ggxm-9mc5
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: >= 4.2, < 4.2.30
Patched in: 4.2.30

Summary: Django vulnerable to ASGI header spoofing via underscore/hyphen conflation

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Tarek Nakkouch for reporting this issue.
GitHub Security Advisory: GHSA-mvfq-ggxm-9mc5
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: >= 5.2, < 5.2.13
Patched in: 5.2.13

Summary: Django vulnerable to ASGI header spoofing via underscore/hyphen conflation

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Tarek Nakkouch for reporting this issue.
GitHub Security Advisory: GHSA-mvfq-ggxm-9mc5
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-290: Authentication Bypass by Spoofing
Vulnerable versions: >= 6.0, < 6.0.4
Patched in: 6.0.4

Summary: Django vulnerable to ASGI header spoofing via underscore/hyphen conflation

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `ASGIRequest` allows a remote attacker to spoof headers by exploiting an ambiguous mapping of two header variants (with hyphens or with underscores) to a single version with underscores.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Tarek Nakkouch for reporting this issue.
GitHub Security Advisory: GHSA-5mf9-h53q-7mhq
Package: Django (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: >= 4.2, < 4.2.30
Patched in: 4.2.30

Summary: Django has potential DoS via MultiPartParser through crafted multipart uploads

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-5mf9-h53q-7mhq
Package: Django (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: >= 5.2, < 5.2.13
Patched in: 5.2.13

Summary: Django has potential DoS via MultiPartParser through crafted multipart uploads

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-5mf9-h53q-7mhq
Package: Django (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-407: Inefficient Algorithmic Complexity
Vulnerable versions: >= 6.0, < 6.0.4
Patched in: 6.0.4

Summary: Django has potential DoS via MultiPartParser through crafted multipart uploads

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. `MultiPartParser` allows remote attackers to degrade performance by submitting multipart uploads with `Content-Transfer-Encoding: base64` including excessive whitespace.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Seokchan Yoon for reporting this issue.
GitHub Security Advisory: GHSA-933h-hp56-hf7m
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 4.2, < 4.2.30
Patched in: 4.2.30

Summary: Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Superior for reporting this issue.
GitHub Security Advisory: GHSA-933h-hp56-hf7m
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 5.2, < 5.2.13
Patched in: 5.2.13

Summary: Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Superior for reporting this issue.
GitHub Security Advisory: GHSA-933h-hp56-hf7m
Package: Django (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: >= 6.0, < 6.0.4
Patched in: 6.0.4

Summary: Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit

Details:
An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. ASGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit when reading `HttpRequest.body`, allowing remote attackers to load an unbounded request body into memory.

Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Superior for reporting this issue.
GitHub Security Advisory: GHSA-fh64-r2vc-xvhr
Package: mlflow (PIP)
Severity: MODERATE (CVSS 5.4)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: <= 3.10.1
Patched in: 3.11.1

Summary: MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface

Details:
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. 

This issue affects MLflow version through 3.10.1
GitHub Security Advisory: GHSA-w8wv-vfpc-hw2w
Package: nicegui (PIP)
Severity: MODERATE (CVSS 5.9)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 3.9.0
Patched in: 3.10.0

Summary: NiceGUI: Upload filename sanitization bypass via backslashes allows path traversal on Windows

Details:
### Summary

The upload filename sanitization introduced in GHSA-9ffm-fxg3-xrhh uses `PurePosixPath(filename).name` to strip path components. Since `PurePosixPath` only recognizes forward slashes (`/`) as path separators, an attacker can bypass this sanitization on Windows by using backslashes (`\`) in the upload filename.

Applications that construct file paths using `file.name` (a pattern demonstrated in NiceGUI's bundled examples) are vulnerable to arbitrary file write on Windows.

### Details

The sanitization in `nicegui/elements/upload_files.py` uses:

```python
filename = PurePosixPath(upload.filename or '').name
```

`PurePosixPath` treats backslashes as literal characters, not path separators:

```python
>>> PurePosixPath('..\\..\\secret\\evil.txt').name
'..\\..\\secret\\evil.txt'  # Not stripped!
```

When this filename is used in a path operation on Windows (e.g., `Path('uploads') / file.name`), Windows `Path` interprets backslashes as directory separators, resolving the path outside the intended directory.

### Impact

On Windows deployments of NiceGUI applications that use `file.name` in path construction:

- **Arbitrary file write** outside the intended upload directory
- **Potential remote code execution** through overwriting application files or placing executables in known locations
- **Data integrity loss** through overwriting existing files

Linux and macOS are not affected, as they treat backslashes as literal filename characters.
GitHub Security Advisory: GHSA-pr46-2v3c-5356
Package: emmett (PIP)
Severity: HIGH (CVSS 7.5)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 2.5.0, < 2.8.1
Patched in: 2.8.1

Summary: Emmett has a path traversal in internal assets handler

Details:
The RSGI static handler for Emmett's internal assets (`/__emmett__` paths) is vulnerable to path traversal attacks.

An attacker can use `../` sequences (eg `/__emmett__/../rsgi/handlers.py`) to read arbitrary files outside the assets directory.
GitHub Security Advisory: GHSA-46r5-x6jq-v8g6
Package: mlflow (PIP)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-862: Missing Authorization
Vulnerable versions: <= 3.10.1
Patched in: unpatched

Summary: MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint

Details:
MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint used to download saved model artifacts. Due to missing access‑control validation, a user without permissions to a given experiment can directly query this endpoint and retrieve model artifacts they are not authorized to access.

 
This issue affects MLflow version through 3.10.1
GitHub Security Advisory: GHSA-69w3-r845-3855
Package: transformers (PIP)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: < 5.0.0rc3
Patched in: 5.0.0rc3

Summary: HuggingFace Transformers allows for arbitrary code execution in the `Trainer` class

Details:
A vulnerability in the HuggingFace Transformers library, specifically in the `Trainer` class, allows for arbitrary code execution. The `_load_rng_state()` method in `src/transformers/trainer.py` at line 3059 calls `torch.load()` without the `weights_only=True` parameter. This issue affects all versions of the library supporting `torch>=2.2` when used with PyTorch versions below 2.6, as the `safe_globals()` context manager provides no protection in these versions. An attacker can exploit this vulnerability by supplying a malicious checkpoint file, such as `rng_state.pth`, which can execute arbitrary code when loaded. The issue is resolved in version v5.0.0rc3.
GitHub Security Advisory: GHSA-8ffj-4hx4-9pgf
Package: lightrag-hku (PIP)
Severity: MODERATE (CVSS 4.2)
CWE: CWE-347: Improper Verification of Cryptographic Signature
Vulnerable versions: <= 1.4.13
Patched in: 1.4.14

Summary: lightrag-hku: JWT Algorithm Confusion Vulnerability 

Details:
## Summary
The LightRAG API is vulnerable to a JWT algorithm confusion attack where an attacker can forge tokens by specifying 'alg': 'none' in the JWT header. Since the `jwt.decode()` call does not explicitly deny the 'none' algorithm, a crafted token without a signature will be accepted as valid, leading to unauthorized access.

## Details
In `lightrag/api/auth.py` at line 128, the `validate_token` method calls:

```python
payload = jwt.decode(token, self.secret, algorithms=[self.algorithm])
```

This allows any algorithm listed in the token's header to be processed, including 'none'. The code does not explicitly specify that 'none' is not allowed, making it possible for an attacker to bypass authentication.

## PoC
An attacker can generate a JWT with the following structure:

```json
{
  "header": {
    "alg": "none",
    "typ": "JWT"
  },
  "payload": {
    "sub": "admin",
    "exp":[PII_REDACTED],
    "role": "admin"
  }
}
```

Then send a request like:

```bash
curl -H "Authorization: Bearer eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiJhZG1pbiIsImV4cCI6MTcwMDAwMDAwMCwicm9sZSI6ImFkbWluIn0." http://localhost:8000/api/protected-endpoint
```

## Impact
An attacker can impersonate any user, including administrators, by forging a JWT with 'alg': 'none', gaining full access to protected resources without needing valid credentials.

## Recommended Fix
Explicitly specify allowed algorithms and exclude 'none'. Modify the `validate_token` method to:

```python
allowed_algorithms = [self.algorithm] if self.algorithm != 'none' else ['HS256', 'HS384', 'HS512']
payload = jwt.decode(token, self.secret, algorithms=allowed_algorithms)
```

Or better yet, hardcode the expected algorithm(s):

```python
payload = jwt.decode(token, self.secret, algorithms=['HS256'])
```
GitHub Security Advisory: GHSA-23jg-5f8m-gw8c
Package: pyblade (PIP)
Severity: LOW (CVSS 6.3)
CWE: CWE-791: Incomplete Filtering of Special Elements
Vulnerable versions: >= 0.1.8-alpha, <= 0.2.0-alpha
Patched in: unpatched

Summary: PyBlade: SSTI/RCE via Bypassed AST Validation in sandbox.py

Details:
A vulnerability has been found in AntaresMugisho PyBlade 0.1.8-alpha/0.1.9-alpha. The affected element is the function _is_safe_ast of the file sandbox.py of the component AST Validation. Such manipulation leads to improper neutralization of special elements used in a template engine. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
GitHub Security Advisory: GHSA-r758-8hxw-4845
Package: justhtml (PIP)
Severity: LOW (CVSS 0.0)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Vulnerable versions: >= 1.13.0, < 1.14.0
Patched in: 1.14.0

Summary: justhtml: Mutation XSS with custom foreign-namespace sanitization policies

Details:
## Summary

A parser-differential / mutation XSS issue was found in `justhtml` when using a **custom sanitization policy** that preserves foreign namespaces such as SVG or MathML.

Under these custom settings, specially crafted input could sanitize into HTML that looked safe at first, but became unsafe when parsed again by a browser or another HTML parser.

## Impact

This issue does **not** affect the default safe configuration.

You may be affected if you use a custom `SanitizationPolicy` with settings like:

- `drop_foreign_namespaces=False`
- allowlisted foreign elements such as MathML or SVG
- allowlisted raw-text containers such as `<style>`

In that case, an attacker could inject markup that survives sanitization and turns into active HTML after re-parsing.

## Affected versions

- `justhtml` `<= 1.13.0`

## Fixed version

- Fixed in `1.14.0`

## Workarounds

Until you upgrade:

- keep `drop_foreign_namespaces=True`
- avoid allowlisting foreign namespaces for untrusted input
- avoid allowlisting raw-text containers such as `<style>` in custom policies

## Notes

The default `JustHTML(..., sanitize=True)` behavior was not found to be vulnerable in this issue.

## Credit

Discovered by JustHTML author during a LLM-based security review of `justhtml`.
GitHub Security Advisory: GHSA-69x8-hrgq-fjj8
Package: litellm (PIP)
Severity: HIGH (CVSS 0.0)
CWE: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, CWE-327: Use of a Broken or Risky Cryptographic Algorithm, CWE-916: Use of Password Hash With Insufficient Computational Effort
Vulnerable versions: < 1.83.0
Patched in: 1.83.0

Summary: LiteLLM: Password hash exposure and pass-the-hash authentication bypass

Details:
### Impact

Three issues combine into a full authentication bypass chain:

1. Weak hashing: User passwords are stored as unsalted SHA-256 hashes, making them vulnerable to rainbow table attacks and trivially identifying users with identical passwords.
2. Hash exposure: Multiple API endpoints (/user/info, /user/update, /spend/users) return the password hash field in responses to any authenticated user regardless of role. Plaintext passwords could also potentially be exposed in certain scenarios.
4. Pass-the-hash: The /v2/login endpoint accepts the raw SHA-256 hash as a valid password without re-hashing, allowing direct login with a stolen

An already authenticated user can retrieve another user's password hash from the API and use it to log in as that user. This enables full privilege escalation in three HTTP requests.

### Patches

Fixed in v1.83.0. Passwords are now hashed with scrypt (random 16-byte salt, n=16384, r=8, p=1). Password hashes are stripped from all API responses. Existing SHA-256 hashes are transparently migrated on next login.
GitHub Security Advisory: GHSA-rgq9-fqf5-fv58
Package: sglang (PIP)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: <= 0.5.9
Patched in: 0.5.10

Summary: SGLang's multimodal generation module is vulnerable to unauthenticated remote code execution through the ZMQ broker

Details:
SGLang's multimodal generation module is vulnerable to unauthenticated remote code execution through the ZMQ broker, which deserializes untrusted data using pickle.loads() without authentication.
GitHub Security Advisory: GHSA-jx93-g359-86wm
Package: sglang (PIP)
Severity: CRITICAL (CVSS 9.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: <= 0.5.9
Patched in: 0.5.10

Summary: SGLang's encoder parallel disaggregation system is vulnerable to unauthenticated remote code execution through the disaggregation module

Details:
SGLang's encoder parallel disaggregation system is vulnerable to unauthenticated remote code execution through the disaggregation module, which deserializes untrusted data using pickle.loads() without authentication.
GitHub Security Advisory: GHSA-hvwj-8w5g-28rg
Package: sglang (PIP)
Severity: HIGH (CVSS 7.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: <= 0.5.9
Patched in: 0.5.10

Summary: SGLangs `replay_request_dump.py` contains an insecure pickle.load() without validation and proper deserialization

Details:
SGLangs `replay_request_dump.py` contains an insecure pickle.load() without validation and proper deserialization. An attacker can take advantage of this by providing a malicious .pkl file, which will execute the attackers code on the device running the script.