# Chosen Ciphertext Attack in Jose4j

Advisory record · `GHSA-jgvc-jfgh-rjvv`

- **Identifiers:** `GHSA-jgvc-jfgh-rjvv`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 27 Apr 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Apr 2023, 23:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.bitbucket.b_c:jose4j` (Maven): affected `<0.9.3`; fixed in `0.9.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> RSA1_5 decryption in the Maven package org.bitbucket.b_c:jose4j, versions before 0.9.3, is susceptible to chosen ciphertext attacks. An attacker who can submit modified ciphertexts and observe the decryption results can learn whether the decrypted message has valid PKCS #1 padding, which may allow decrypting RSA1_5 or RSA_OAEP encrypted content. Upgrade to version 0.9.3 or later. The source gives few details on the attack's exact conditions.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jgvc-jfgh-rjvv)

## Sources

- [GitHub Advisory Database: GHSA-jgvc-jfgh-rjvv](https://github.com/advisories/GHSA-jgvc-jfgh-rjvv)
- [OSV: GHSA-jgvc-jfgh-rjvv](https://osv.dev/vulnerability/GHSA-jgvc-jfgh-rjvv)
- <https://github.com/google/security-research/security/advisories/GHSA-jgvc-jfgh-rjvv>
- <https://bitbucket.org/b_c/jose4j/commits/14e62a8dee9decb4ff6e0625aedc5724601bfdb6>
- <https://bitbucket.org/b_c/jose4j/commits/63b86581e7bfcc2d9d04ee15caea4b5bfb911f59>
- <https://bitbucket.org/b_c/jose4j/commits/tag/jose4j-0.9.3>
- <https://github.com/google/security-research>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jgvc-jfgh-rjvv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jgvc-jfgh-rjvv/>. Everything for agents: <https://agentprime.io/llms.txt>.
