As someone who has to track down things like this constantly, I'm pretty unimpressed at the (lack of) speed of their code checking. This was not an obscure bug or complicated. It was just a too-large buffer definition and an execution path that always downloaded info.
<snip>
Again unimpressed. There've been accurate explanations posted here before Apple spoke up, that took just minutes to compose.
So with a large company that carefully crafts it's image, there's a lot of small delays, especially if nobody worked through the weekend on this.
Odds are that the investigation didn't start until Thursday and a report given on Friday. There may have been discussions on Friday as to what options there were to address this. This would be the lovely political debates on when to fix it, how to get it to customers, test resources, etc. The sign-off on this plan likely happened late Friday and possibly Monday. Keep in mind they are rolling out what amounts to an unplanned dot-release for this.
The signed-off plan would then be handed off to the high-level management on Monday, to be word-smithed, passed through their legal advisors and so on. They were probably ready to go Tuesday and decided to line up the interview and press release for early Wednesday so that they could see the reactions through the day instead of being at home trying to sleep when it was all getting released.
This of course assumes that nobody worked through the weekend on it (wouldn't surprise me that nobody did). This also assumes that they noticed that what was reported didn't seem right, and they decided to hold off on a "by design" e-mail before they knew for sure what was going on.
Sure, you can get an answer quicker, but how many of us need to have our words about Apple cleared by their lawyers?