[Security] HIGH: 2 issue(s) found in kimi_agent_glyph_submission_bug #1

New issue

Closed

opened 2026-05-14 23:23:35 +00:00 by Mark · 1 comment

Mark commented

2026-05-14 23:23:35 +00:00

Owner

Security Scan Results for `kimi_agent_glyph_submission_bug`

Severity: HIGH
Findings: 2

1. secret_in_diff

Details: Potential Password in URL found in commit 77bad14a
Commit: 77bad14a
Pattern: Password in URL

2. secret_in_diff

Details: Potential AWS Secret Key found in commit 053f9499
Commit: 053f9499
Pattern: AWS Secret Key

This issue was auto-generated by the security sweep cron job.

## Security Scan Results for `kimi_agent_glyph_submission_bug` **Severity:** HIGH **Findings:** 2 ### 1. secret_in_diff - **Details:** Potential Password in URL found in commit 77bad14a - **Commit:** `77bad14a` - **Pattern:** `Password in URL` ### 2. secret_in_diff - **Details:** Potential AWS Secret Key found in commit 053f9499 - **Commit:** `053f9499` - **Pattern:** `AWS Secret Key` --- *This issue was auto-generated by the security sweep cron job.*

Mark added the

blocked:needs-decision

label

2026-05-15 17:00:44 +00:00

Mark commented

2026-05-16 06:43:22 +00:00

Author

Owner

Risk accepted. Both findings are in private tailnet-only infrastructure:

Password in URL — Forgejo token in git history, only usable on internal tailnet instance. No external exposure.
AWS Secret Key — false positive in package-lock.json bootstrap artifact.

No purge or rotation needed.

**Risk accepted.** Both findings are in private tailnet-only infrastructure: 1. **Password in URL** — Forgejo token in git history, only usable on internal tailnet instance. No external exposure. 2. **AWS Secret Key** — false positive in package-lock.json bootstrap artifact. No purge or rotation needed.

Mark closed this issue

2026-05-16 06:43:25 +00:00