# CVE-2026-112148: A vulnerability has been identified in LIFF SDK versions 2.20.0 through 2.31.0, where a DOM-based cross-site scripting (XSS) flaw allows an


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026

## What is CVE-2026-112148?

CVE-2026-112148 is a medium-severity vulnerability in LY Corporation LIFF SDK, published on 20 Oct 2026. 

### Official description

A vulnerability has been identified in LIFF SDK versions 2.20.0 through 2.31.0, where a DOM-based cross-site scripting (XSS) flaw allows an attacker to execute arbitrary JavaScript in the origin of an affected LIFF application's endpoint when a user opens a specially crafted URL in an external browser, potentially leading to disclosure of JavaScript-accessible authentication tokens or application data, or unauthorized actions using the user's session.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-112148?


## How do I fix CVE-2026-112148?

No fix has been published for CVE-2026-112148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112148 being exploited?

There is no known exploitation of CVE-2026-112148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112148 and fix it if it is affected.

What it is: CVE-2026-112148 is a medium-severity vulnerability in LY Corporation LIFF SDK, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112148 in the wild and no public exploit code.

Affected product: LY Corporation LIFF SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112148/ (Markdown: https://insights.sbomify.com/CVE-2026-112148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112148
- OSV: https://osv.dev/vulnerability/CVE-2026-112148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112148/
Summaries are generated and may contain mistakes; the official description above is the record.