An idea like this was actually raised by Mercury Interactive sales guys when visiting our company on one occasion...
The idea was to implant a WebDefectManager "control" into a screen in our online app. This would allow customers to log any problems they were having using our app and track bugs they had reported through to resolution (in a kind of 'outsourced test' move).
The idea of "admitting" to having bugs in our software, let alone broadcasting the matter went down like a lead balloon with the managers here! (not unsuprisingly!)
I can see how that would have been received Automatrix
My suggestion would be to only post it if:
1) It had been verified.
2) The impact of the bug had been accessed.
3) There was a fix in the works.
4) You had an ETA as to when the fix would be launched.
That way, your customers wouldn't feel as if they were testing your site / product for you. They would also know that you were actively addressing their concerns.
In today's market where there are 20 other companies offering alternatives to your products, we cannot afford to 'tick off' our customers. Let them know that you're supporting them and they'll stay around
But my original post still stands in that you shouldn't embellish your statements - just the facts so you don't make it seem any bigger than it really is and that it is being addressed in a timely manner.