# CVE-2026-117679: CVE-2026-117679

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

A cross-site scripting vulnerability exists in SHIRASAGI, which may allow an authenticated attacker to execute arbitrary script in a user's web browser when the user accesses a website using the affected product.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- SHIRASAGI Project / SHIRASAGI: ≥ v1.12.0; ≤ v1.21.0 (affected, semver). Source: CNA: jpcert

## Severity and prioritization

- CVSS 3.0: 5.4 (medium); CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N; source: CNA: jpcert

- CVSS 4.0: 5.1 (medium); CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N; source: CNA: jpcert

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.ss-proj.org/support/1743.html (CNA: jpcert)

- https://jvn.jp/en/jp/JVN55454512/ (CNA: jpcert)

## Provenance

- CNA: jpcert: https://www.cve.org/CVERecord?id=CVE-2026-117679; retrieved 2026-11-05; source updated 2026-11-05

Revision: f60bacd4d4f5981ce22fd3263eb7ccba7ba3e2d2a9db996d2bd59bf732376647

Canonical: https://y2.dev/cve/CVE-2026-117679

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.