This is not what I read at all. They just did a bookkeeping mistake, that prevented the fix from coming in the security releases, which I can only assume has a quick release cycle.

> The mistake we made was marking this bug for "next" release, which is the soon to be released Flash Player 10.1, instead of marking it for the next Flash Player 10 security dot release.