Vulnerabilities

Vulnerability · CVE-2025-55136

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

Published Aug 7, 2025 · catalog updated Aug 7, 2025 · ERC

Last checked Oct 28, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-55136. EPSS is 0.16%. Act only if a listed version of ERC is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.16%
Remediation
Vendor / distro source
Affected products
vendor tae898 ERC 0 ≤0.3

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor tae898 ERC 0 ≤0.30 ≤0.3

How to fix CVE-2025-55136

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-55136. EPSS is 0.16%. Act only if a listed version of ERC is installed.

Which versions are affected?

Compare what you have installed with tae898 ERC 0 ≤0.3 0 ≤0.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.16%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 7, 2025 · EUVD

    Detected

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

  2. Aug 7, 2025 · EUVD

    Updated

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

Sources

  • CVE.orgVulnerability recordCVE-2025-55136

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-55136

    30-day exploitation probability 0.16%

    first.org
  • EUVDVulnerability recordEUVD-2025-23928

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

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 28, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 28, 2026
  • CVE.orgOct 21, 2026
  • EUVDOct 20, 2026