Improperly Controlled Modification of Dynamically-Determined Object Attributes Affecting neo4j-2026.07 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.45% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-NEO4J202607-19787165
  • published15 Sept 2026
  • disclosed23 Jun 2026

Introduced: 23 Jun 2026

CVE-2026-54516  (opens in a new tab)
CWE-915  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest neo4j-2026.07.

NVD Description

Note: Versions mentioned in the description apply only to the upstream neo4j-2026.07 package and not the neo4j-2026.07 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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, POJOPropertiesCollector._renameProperties() allows a property with @JsonProperty("renamed") on the getter and @JsonIgnore on the setter to be renamed rather than dropped. With MapperFeature.INFER_PROPERTY_MUTATORS enabled (default), the private backing field is retained; during deserialization BeanDeserializerFactory.addBeanProps() sees hasField()==true, builds a FieldProperty, and makes the backing field writable. An attacker supplying the renamed JSON key writes the backing field directly, bypassing the @JsonIgnore on the setter. This vulnerability is fixed in 3.1.4.

CVSS Base Scores

version 3.1