{"vulnerability": "CVE-2026-48203", "sightings": [{"uuid": "22b91d6a-73f4-49ec-a6fc-2e50c9510a85", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48203", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3mpwg6pj4kz2a", "content": "CVE-2026-48203: Apache Camel: Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to inject Solr query parameters (server-side request forgery) and document fields", "creation_timestamp": "2026-07-05T20:31:08.779392Z"}, {"uuid": "09786bff-5895-414c-9d7b-9987707a521f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-48203", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mpywpgyich2h", "content": "CVE-2026-48203 - apache camel\nApache Camel Solr's security filter failed to block certain header names, allowing an attacker to inject malicious data into Solr queries and indexed documents.\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#apachecamel #apachefoundation #CVE #infosec", "creation_timestamp": "2026-07-06T20:32:04.748255Z"}]}