Skip to content
Fencer Intel
high 7.5

CVE-2019-18848 json

JSON-jwt Gem lacked element count during splitting of JWE string

published 6y ago modified 4mo ago also GHSA-cff7-6h4q-q5pj , EUVD-2019-0742

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string.

Patch / fix

  • rubygems json-jwt 1.11.0
  • json-jwt_project json-jwt 1.11.0
  • ruby-json-jwt Debian 14, Debian 13, Debian 12 1.11.0-1

debian advisories DEBIAN-CVE-2019-18848

  • rubygem-json-jwt Package Hub 15 SP5, openSUSE Leap 15.5 1.16.6-bp155.3.3.1
  • rubygem-aes_key_wrap Package Hub 15 SP5, openSUSE Leap 15.5 1.1.0-bp155.2.1

opensuse advisories openSUSE-SU-2025:0004-1

Is CVE-2019-18848 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems json-jwt
<1.11.0
1.11.0

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.