I've found it, it has to do with entity acces. The role who creates object didn't had read/write access to the attribute.
Instead of throwing an error, the attribute was filled with the default value (50000).
Based on what you describe; it appears to be a bug