# CVE-2026-54517: jackson-databind: @JsonView bypass for setterless creator properties > Attackers can bypass @JsonView restrictions to access restricted setterless collection properties in jackson-databind, leading to unauthorized data exposure. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Jun 2026 - **Updated:** 24 Jun 2026 - **Also known as:** CLEANSTART-2026-AL85661, CLEANSTART-2026-VQ66047, CLEANSTART-2026-WC26627, CLEANSTART-2026-XQ97878, CLEANSTART-2026-XX16002, DEBIAN-CVE-2026-54517, ECHO-6681-8823-c8a0, GHSA-5hh8-q8hv-fr38, MINI-247g-6x8j-9895, MINI-275r-qxj6-j8gq, MINI-292j-93mg-c5vm, MINI-2mxf-x526-99cm, MINI-2rr7-xhqj-9vfx, MINI-49jp-4gw5-3rcf, MINI-4q8v-gr43-cfpp, MINI-5f3j-4h2f-hv7q, MINI-6cmc-5p59-gqc9, MINI-76mq-vw3g-5w3c, MINI-7j7q-ccw3-rhgr, MINI-7p7x-8gw5-jrfq, MINI-7xm5-qfv2-pv34, MINI-9g4r-wfjj-w45v, MINI-9rrr-2pp4-pxp6, MINI-fmpp-5w5x-gcgq, MINI-g5hc-m3hw-vqx5, MINI-h6mq-4rcf-pr5p, MINI-jw3w-m4vf-pc6w, MINI-m3hw-g7gx-pwcx, MINI-m8w4-9fg9-hw87, MINI-mpvg-ccfw-qqqx, MINI-mqvq-fw5c-v834, MINI-p7fj-g5g8-38wf, MINI-p7rq-j2w9-qqhf, MINI-pfgf-rw8h-fvg9, MINI-pmww-xgv7-xhcg, MINI-px4x-xcgh-g996, MINI-q2pc-rh4f-m38v, MINI-q3p9-pmwr-xgp3, MINI-qq7p-wf84-v52f, MINI-rrmv-3f8g-6pwx, MINI-v5xw-rfcq-q4m8, MINI-vf59-rwjw-jg95, MINI-vg92-823w-9mcm, MINI-vp2w-wc4f-9hmq, MINI-x995-4cx8-fjcw, MINI-xmpc-3jf6-m6xg, MINI-xq4w-f7x2-wcg3, MINI-xqpq-25hh-7grv, ROOT-APP-MAVEN-CVE-2026-54517, UBUNTU-CVE-2026-54517 ## What is CVE-2026-54517? CVE-2026-54517 is a medium-severity vulnerability in Fasterxml Jackson-Databind, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.21.0 until 2.21.4 and 3.1.4, in BeanDeserializer._deserializeUsingPropertyBased, the active-view (@JsonView) filter was applied only to creator properties; the regular property-buffering branch performed no prop.visibleInView(activeView) check. A change making SetterlessProperty.isMerging() return true routed setterless Collection/Map properties through this unguarded path, so a setterless collection annotated with a restricted @JsonView is populated from attacker JSON even when the active view excludes it. This vulnerability is fixed in 2.21.4 and 3.1.4. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2026-54517? 6 open source packages ship an affected version, including com.fasterxml.jackson.core:jackson-databind and tools.jackson.core:jackson-databind. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.fasterxml.jackson.core:jackson-databind` | Maven | From 2.21.0 | 2.21.4 | | `com.fasterxml.jackson.core:jackson-databind` | Maven | From 2.21.0 | 2.21.4 | | `com.fasterxml.jackson.core:jackson-databind` | Maven | From 3.0.0 | 3.1.4 | | `com.fasterxml.jackson.core:jackson-databind` | Maven | From 3.0.0 | 3.1.4 | | `tools.jackson.core:jackson-databind` | Maven | From 3.0.0 | 3.1.4 | | `tools.jackson.core:jackson-databind` | Maven | From 3.0.0 | 3.1.4 | Products: Fasterxml Jackson-Databind. ## How do I fix CVE-2026-54517? Upgrade com.fasterxml.jackson.core:jackson-databind to a fixed version for your release line: 2.21.4 or 3.1.4. ## Is CVE-2026-54517 being exploited? There is no known exploitation of CVE-2026-54517 in the wild and no public exploit code. ## Other vulnerabilities in Fasterxml Jackson-Databind - [CVE-2018-11307](https://insights.sbomify.com/CVE-2018-11307/): Deserialization of Untrusted Data in jackson-databind (critical 9.8) - [CVE-2026-54512](https://insights.sbomify.com/CVE-2026-54512/): jackson-databind: PolymorphicTypeValidator bypass via generic type parameters allows arbitrary class instantiation (high 8.1) - [CVE-2026-54513](https://insights.sbomify.com/CVE-2026-54513/): jackson-databind: Array subtype allowlist bypass in BasicPolymorphicTypeValidator (allowIfSubTypeIsArray) (high 8.1) - [CVE-2020-14060](https://insights.sbomify.com/CVE-2020-14060/): Deserialization of untrusted data in Jackson Databind (high 8.1) - [CVE-2021-46877](https://insights.sbomify.com/CVE-2021-46877/): jackson-databind possible Denial of Service if using JDK serialization to serialize JsonNode (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54517 and fix it if it is affected. What it is: CVE-2026-54517 is a medium-severity vulnerability in Fasterxml Jackson-Databind, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-54517 in the wild and no public exploit code. Affected packages and fixed versions: - com.fasterxml.jackson.core:jackson-databind (Maven): affected from 2.21.0; fixed in 2.21.4 - com.fasterxml.jackson.core:jackson-databind (Maven): affected from 2.21.0; fixed in 2.21.4 - com.fasterxml.jackson.core:jackson-databind (Maven): affected from 3.0.0; fixed in 3.1.4 - com.fasterxml.jackson.core:jackson-databind (Maven): affected from 3.0.0; fixed in 3.1.4 - tools.jackson.core:jackson-databind (Maven): affected from 3.0.0; fixed in 3.1.4 - tools.jackson.core:jackson-databind (Maven): affected from 3.0.0; fixed in 3.1.4 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-54517/ (Markdown: https://insights.sbomify.com/CVE-2026-54517/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54517 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54517 - OSV: https://osv.dev/vulnerability/CVE-2026-54517 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54517/ Summaries are generated and may contain mistakes; the official description above is the record.