`POST /{owner}/{repo}/topics` was registered without the sig… (CVE-2026-107618)

Summary

Vulnerability reported (CVE-2026-107618). Risk of unauthorized operations or information disclosure. Exploitable via POST /{owner}/{repo}/topics.

Original description

The description as published by the source.

POST /{owner}/{repo}/topics was registered without the sign-in middleware that provides the cross-origin protection, so a request issued by a third-party site was not rejected. A repository administrator who visited a malicious page could have the topics of their repository changed. No other repository settings were reachable through this route.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107618 has been found.
Attackers can target a specific entry point like POST /{owner}/{repo}/topics over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-107618" on the vendor's site.

CVE-2026-107618
Attack surface: POST /{owner}/{repo}/topics
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) has been reported. Attackers reach the vulnerable code path via POST /{owner}/{repo}/topics.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: POST /{owner}/{repo}/topics.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /{owner}/{repo}/topics requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Hunt for indicators of compromise detect
```
grep 'POST /{owner}/{repo}/topics' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで POST /{owner}/{repo}/topics への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Post-deployment verification verify
```
Replay attack against POST /{owner}/{repo}/topics on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

`POST /{owner}/{repo}/topics` was registered without the sign-in middleware that provides the cross-origin protection…

Summary

Original description

Auto-generated summary

Response actions

References